- 199comments
- 591comments
- 23comments
- 205comments
- 89comments
- 59comments
- 8comments
- 1comments
- 61comments
- 610comments
- —discuss
- 20comments
- 31comments
- 1comments
- 51comments
- 151comments
- 140comments
- 303comments
- 367comments
- 1comments
- 221comments
- 166comments
- 30comments
- 98comments
- 56comments
- 25comments
- 28comments
- 127comments
- 64comments
- 133comments
Came here for a five-gallon bucket hooked to Dulwich (archiving rain?), Slightly disappointed :)
Go Git and Dulwich and friends are indeed fun tech.
Most of the pain here is the typical set of issues people run into trying to make S3 a filesystem as-is, common with S3FS-family approaches.
ZeroFS (https://github.com/Barre/zerofs) is 9P/NFS/NBD over S3 on an LSM. Point stock go-git, or just /usr/bin/git, at a mount and skip the gymnastics. Rename is a metadata op in the keyspace, so you get it atomic on any S3, no Tigris-specific X-Tigris-Rename needed.
Different point on the spectrum, but less square-peg, also most probably much, much faster (it works great on linux-sized repos) :)
Author of the article here. I'm aware of ZeroFS and other similar approaches (such as something internal at Tigris that will become public at a later date), this was more of an experiment to see how far you can get with stuff I already had "on the shelf". I am going to be improving this a fair bit; I just need to plan out what I'm gonna work on and figure out the best times to stream it, etc.
I wouldn’t call it gymnastics. The surprising part of the article was that Git itself is an object store that happens to use a filesystem for persistence, but an S3 bucket might actually be more suitable than a .git directory on POSIX.
It makes sense, similar to how blob storage is a natural fit for a nix cache, where you have a giant flat space of many hash-address immutable directories/archives.
I think most of the pain documented in the article is just that git-the-implementation contains a lot of assumptions about it being a (local) filesystem that it is operating on, hence stuff like calling stat a ton of times, or doing the rename trick to get atomic behavior from a not-normally-atomic operation (updating a file in place).
If it were possible to define a "backing storage" API layer within git, it might be possible to move all the filesystem/posix-centric stuff to the other side of it and leave behind an interface that maps quite nicely to blob storage.
Would probably be great to have ZeroFS backed PVs for the K8s folks :)
It's there! https://www.zerofs.net/docs/kubernetes-csi
If you want to store a git repo on S3, you can that with git-annex[1] today. It can do client side encryption and large files as well.
[1] https://git-annex.branchable.com
This was really thought provoking — it made me realize that Git just happens to use a filesystem for persistence, but doesn’t necessarily have to. A POSIX filesystem might not even be the best way to store a git repo. Makes me wonder: what else could speak Git + POSIX? Redis? Postgres? IPFS is a fun one — it’s already content addressed.
IPFS would be much better for something like LFS support than git repos itself. Git repos are very mutable bits of state and IPFS is best for immutable state. I'm aware of mutable IPFS pointers, but I think the best bet currently is to use immutable things for immutable objects and mutable things for mutable objects.
I've seen a few people on HackerNews swear by Fossil ( https://en.wikipedia.org/wiki/Fossil_(software) ) which uses SQLite as the backend instead of the filesystem. There are a few other approaches as well
I did something similar, though a full reimplementation of a git and git-lfs library in Elixir. Still a work in progress though as the S3 backend isn't quite complete and there are performance problems doing some git things through S3.
https://anvil.fangorn.io/fangorn/ex_git_objectstore
The documentation isn't quite correct, but it's getting there
Similar story. A PHP implementation of the Git protocol for self-hosted repositories:
https://repo.autonoma.ca/repo/treetrek/tree/HEAD/git
Great work, though I wish some of this work could be upstreamed to Gitea instead?
Author of the post here. I'll talk with someone I know at Gitea. I don't think this is viable to upstream into Gitea, but there's only one way to find out!
I've been using git-remote-s3 (https://github.com/awslabs/git-remote-s3) which I believe was inspired by this git-remote-s3 (https://crates.io/crates/git-remote-s3).
Not exactly the same thing, but along the same lines of "git and s3 are both object stores, why not use s3 as git storage?"
I’m not sure I understand what pain point this solves. What’s the value of doing this? Is it at a certain scale?