✧✦Catherine✦✧one of the reasons it's useful that git-pages is so efficient storage-wise is that i don't actually need to worry about what people are uploading. there are no cases where reasonable-seeming use of the website would generate problematic amounts of resource use, so i don't have to watch over resource use. it's Fine.
someone uploaded two copies of a site containing Every Manpage, which is half a gigabyte (each)? it only costs 36 MB to store it (total). it's Fine.
by designing the whole thing with scale and efficiency in mind, i can be providing a hyperscale-style service without having hyperscale infrastructure, and i think that's a worthy achievement
jbm@whitequark As someone who's done a bit of scale here and there over the decades, I can definitely appreciate it. It's nicely done.
I also like this project because maybe it means I can finally let go of this long-neglected project: https://joshisanerd.com/projects/undertaker/ (tl;dr: adds tooling to make it a single command to generate the site, with a static HTTP git repo, and then scp/sftp/whatever-s it up. I don't think I've sent this your way before, apologies if I have.)
@AJ9BM ah yeah definitely! also re: archivability, git-pages lets you download the entire thing from the /.git-pages/archive.tar endpoint (although not in all cases because of concerns about enumeration)