git-fat

I've always liked the simplicity of git-fat [0]: * Initial setup includes git filter rules so that "git add" automatically uses get-fat for matching files (no need to remember to invoke git-fat when adding/changing files). * It works by rsync'ing to/from the remote. The setup for this is in a single ".gitfat" file, separate from the filter rules. * You do need to run "git fat push" and "git fat pull"; this can probably be automated with hooks. So just offhand without even trying to think about the "right" way to do what you want, the committed ".gitfat" could be to a read-only remote, then you can swap it with your own un-committed file for a push that has an rsync-writeable remote. Also, the whole thing is a single 628-line python file, so worst case it would be easy to tweak it to read something like ".gitfat-push" and not have to manu

I think it is much closer to git-fat [1] (as jefurii mentions). I've been trying out git-fat on a large repository that has some binaries in it. Since we are already using ssh to access the server (and have the usual ssh-agent setup), it was easy to integrate it with scp. Unfortunately, the performance for our workload (45K files, 5GB total) with git-fat wasn't much different than plain git. It seems most of my problems stem from the number of files, rather than the size. If I had a smaller number of very large files, git-fat might be a good solution. [1] https://github.com/jedbrown/git-fat

Hello All, We've currently got a large repository we'd like to maintain in git. By 'large', I mean 45000 files, and 5GB in disk space. The files consist of source code as well as binaries (compilers, other tools, compiled libraries, etc.). I'd prefer to just keep all this in a single git repository if possible. However, as you may know, git struggles with repositories this large, and operations that normally take milliseconds instead take seconds (or longer). Overall it is not a pleasant experience. I'm aware of other options like Subversion and Perforce that might be a better fit for this, but I'd like to know what are my best options to stay with git. I've used git-submodules, and Google's repo [0] before, and found the workflow with these to be somewhat cumbersome. So far, I've been looking at git-annex [1], git-fat [2], and git-me