Nice. I saw some git-on-durable-objects projects but I'd so much prefer a straight object storage option.

It has been done. It is no longer done because it is not efficient.

Yes, it was not "object storage", but Git can be served from a dumb http server as static files. Now someone figured out that object storage can also serve static files via http. Wow!

On Linux, Fuse is your friend. See eg https://github.com/matthiasgoergens/git-snap-fs

It’s kinda wild to me that this hasn’t been done

https://github.com/awslabs/git-remote-s3

This works seamlessly so you can run `git remote add origin s3://my-git-bucket/my-repo`

Doesn’t Git store data in sparse files? My impression is that git’s on-disk layout is exactly the kind of thing you’d avoid on object storage. Interactions involve a ton of small reads, resulting in poor performance and enormous bills.

It only really makes sense to tarball repos into cold storage on S3 or Glacier, but short of GitLab cloud I suspect there aren’t enough repos cold enough to be worth the dev costs.

S3 that doesn’t have wild costs for git objects sounds like it’s just NFS

After Git At Any Scale there's been a lot of these! (https://cursor.com/blog/git-at-any-scale https://news.ycombinator.com/item?id=49348141)

https://github.com/Nickforall/walgit-elixir https://github.com/tobi/walgit (https://news.ycombinator.com/item?id=49420598) https://github.com/tuist/micelio/

History repeats itself: https://github.com/cjb/GitTorrent

replace whole-file hashes

BLAKE3 has a whole mechanism for this, and as an added bonus it'd be substantially faster.

"Finally delta objects should be stored as their own object in the packfile instead of slapped onto the end of the object it’s a delta of so that you don’t have to read the object and its deltas to read the object in the first place."

Author thinks that delta encoding is there for no reason. Good luck, kid.

Which fonts are you seeing not looking good? It seems perfectly readable sans-serif and monospace wise, but could be system preferences on what fonts to use?

it depends on how much interest was shown, I've definitely posted things and then they get posted again less than 24 hours later and it is that second post that takes off.

`git update-server-info` is your friend; it generates the auxiliary files needed to allow clients to make range requests against packs.

For example: https://andrewaylett.github.io/rgitweb/ is a repository viewer that runs against a static git repo. It doesn't care what you're storing the pack in, just that the data is there to make the right range requests.

I recently found https://github.com/enroute-sh/enroute which also does git on object storage

I found the idea of a git-proxy interesting where you start with proxying an existing forge and then later adopt the object storage backend

Oh this is exactly what I need, fantastic! Thanks for sharing.

This is exactly what GitSocial does: https://gitsocial.org/. Plus it can generate static sites for repositories, letting you serve it all from a bucket.

Or just use https://github.com/Barre/ZeroFS

Works pretty awesomely with git workloads, even Linux sized trees.