Show HN: Git-based front-end interface for Hugo
11–16 of 16 posts
Re: Show HN: Git-based front-end interface for Hugo
#12Re: Show HN: Git-based front-end interface for Hugo
#13Re: Show HN: Git-based front-end interface for Hugo
#14You could have told your LLM to NOT use node/js/npm and made the thing far more secure from day one. Npm is a security nightmare. Also you say it’s git-based but it depends on GitHub. GitHub is not git. What if I want to use another git forge or god forbid a local repo? I have a similar thing but it doesn’t assume GitHub and is coded in Python (by hand, it’s like 100 lines of Python and flask). Serves my needs! Simpl…
Re: Show HN: Git-based front-end interface for Hugo
#15You could have told your LLM to NOT use node/js/npm and made the thing far more secure from day one. Npm is a security nightmare. Also you say it’s git-based but it depends on GitHub. GitHub is not git. What if I want to use another git forge or god forbid a local repo? I have a similar thing but it doesn’t assume GitHub and is coded in Python (by hand, it’s like 100 lines of Python and flask). Serves my needs! Simpl…
As for the tech stack, I chose JS because the main goal was a lightweight web UI that handles online editing and easy image uploads, and JS sounded like a better fit. Having said that, I'm also not happy with current state of npm and I will look into an implementation with Go and tmpl.
Re: Show HN: Git-based front-end interface for Hugo
#16To clarify, this web application only works with repositories hosted on GitHub. Authentication and repository updates are handled entirely through the GitHub API, which allows the app to remain completely stateless, secure, and configuration-free.
Although the idea of making it more generic by supporting different git providers or self-hosted VPS instances is appealing (hence the initial title), there are already much better solutions out there for that use case (like DecapCMS). The goal here was to trade generality for total zero-setup simplicity.