Cannot get Staticman working (using beautifulhugo code but not the whole theme)

[valzi]

I have no errors, but nothing displays in my posts. (See here: https://light-transmuter.netlify.com/posts/4weeks3/) Would you give me suggestions? I feel as if I've read and done everything, but I suspect I am missing something simple. I'm new to Hugo.

Here is the relevant code:
https://github.com/valzi/light-transmuter/blob/master/config.toml
https://github.com/valzi/light-transmuter/blob/master/staticman.yml
https://github.com/valzi/light-transmuter/blob/master/layouts/partials/staticman-comments.html
https://github.com/valzi/light-transmuter/blob/master/layouts/_default/single.html

Here's a sample post.

[valzi]

I have no idea why, but the forms are now showing up. However, submitting a comment generates this error without moving to a new url.

[valzi]

Hey, please let me know if it's rude to bump. Just wanted to check in to say that I've failed to make any progress on my own.

[dancwilliams]

I have statesman working on my site. The repo can be found (here)[https://github.com/dancwilliams/networkhobo].

I am going to review the BeautifulHugo docs, but some things have changed recently with Staticman. Staticman is now a GitHub app. Here are some links. Please read through them all as it is a moving target till the Staticman docs are updated.

eduardoboucas/staticman#243 (comment)
eduardoboucas/staticman#278 (comment)

Let me know if you have any questions. I will help where I can.

[VincentTam]

Hi, this is the maintainer of @staticmanlab, a public GitLab instance.

In your Go-HTML template code, you've hooked your HTML form with the public development instance. Have you considered using api instead of dev due to eduardoboucas/staticman#278 (comment)?

<form method="POST" action="https://dev.staticman.net/v3/entry/github/valzi/light-transmuter/master">

---

Btw, if you goal for the GitHub App version of Staticman is to avoid v2's API limits reported in eduardoboucas/staticman#222, then errors #279 and #294 would serve as counterarguments for this. I suggest using an alternative API instance instead of the official one to avoid unexpected service interruption caused by unnotified updates on the official one. You may choose either self-hosting your own instance or using an existing one.