-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Staticman comments #18
Comments
No, you don't have to. The working source code for the GitLab support was already there on Jul 23. Looking back, if one had forked the commit earlier and ran his/her own Staticman API instance, he/she would be able to post comments on GitLab Pages powered by Staticman without waiting for the future deplyment of Staticman v3 on the public production instance. You may view my sample site, its source code, the source code for my own API instance and Heroku's guide for deploying an existing Node.js app (e.g. Staticman) to Heroku, who provides a free tier including 1000 free hours per month. (24 * 31 < 800). Some documentations: |
@VincentTam hey!! thanks a lot for the info. I have to get time to look at it and implement staticman on my site. It's already implemented but I think it's in a basic way... but I haven't look thoroughly to the MM outdates in my template. |
@luisspuerto The setup guide in the linked PR mixes up GitLab repo config and API server config. An error in his guide is drowned between my discussions with the developer. Therefore, I've just finished writing my GitLab repo setup guide. A custom Staticman server setup guide is upcoming. Hope that helps. |
Hey! Thanks a lot for al the info @VincentTam I'll definitely take it a look in the near future. |
I have to implement Staticman comments. Perhaps I can wait until gitlab implementation finish.
This tool could be interesting too.
Some documentation:
Staticman now supports [threaded comments](url
eduardoboucas/staticman#35) I have to check how mademistakes.com has done it.
The text was updated successfully, but these errors were encountered: