grubby: static site generator for git repos written in Ruby

13 points by bt

telemachus

For people who are curious to see more of this kind of tool, there's reporat, which is another implementation in Ruby.

And from reporat's homepage, some others.

repo2html, written in Chicken Scheme
stagit, written in C
depp, written in Go
git-arr, written in Python
gituwa, written in C

jss

I also saved this one: sorcery, written in Rust from another lobsters thread a few weeks ago

I feel like while the concept is not new, its been picking up some steam recently. Seems like a nice minimalist solution, although I worry about people taking down / not wanting to maintain their hosts long-term causing some software to be lost to time, compared to something like Codeberg that will likely stay around for a while
- lknuth
  
  "How can we bare to throw anything away? "
  
  Maybe that's okay. I like that its in the hands or the authors more.
- k749gtnc9l3w
  
  Isn't it orthogonal? It's good to have cheap-to-serve static options for self-hosting. It is also good if large-ish hosters have efficient options to switch to static-hosted public view, if they decide to.
  
  In some cases it could also make it friendlier to Internet Archive crawling, which could easily flip the preservation analysis…
- jaculabilis
  
  I was just testing out sorcery on my own repos as a potential successor to my little-used Gitea instance. I chose it over stagit and git-arr but hadn't found depp or gituwa, I'll have to evaluate those too.
  
  although I worry about people taking down / not wanting to maintain their hosts long-term causing some software to be lost to time
  
  I think Radicle is trying to solve this problem by creating a network of mirrors, allowing people to contribute their own resources to keeping source code online. I'm not sure it's ready for prime time yet, but I hope they get there or a successor project picks up their torch.
antonmedv

Another repo generator with github like look: https://github.com/antonmedv/gitmal
qznc

I assume this the next escalation level to defend against bots. To be used when I want to publish a repo but not DDOSed?

Doesn't Forgejo provide an options to restrict the public web interface to not show individual commits and stuff just like reporat, grubby, etc?
- bt
  
  To be used when I want to publish a repo but not DDOSed?
  
  That’s certainly part of it. Reducing resource usage, especially on low end servers is another plus!