4 ms·
You 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 b
by loloquwowndueo 5mo ago
You 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! Simple and dumb.
- e-Minguez 5mo agoLink?
- deleted 5mo ago[deleted]
- arashThr 5mo agoAuthor here. You're completely right about the GitHub specific implementation. I made a mistake in the title! Right now only GitHub auth is supported. Although the design should work with any Git repo down the line. Sorry for causing confusion. Unfortunately I can't edit the title now. I will add a comment to explain this limitation. 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.