Yes thanks, I'm aware of git-annex. It is neat and I use it in some contexts (i.e. for images and other largish binary files). But here what I'd like is not storage for files external to git (as git-annex does) but storage precisely for git's objects database.
I'd like to do: $ git remote add grid tahoe:myproject $ git push grid Or: $ git clone tahoe:myproject I'll look at git-annex's code for inspiration but the more I think about it the more I think the git people may have suggestions. Just wondering if anybody here had felt the same need and maybe came up with a solution. * Chris Kerr [2015.10.23 01:56]: > I'm not sure if this is exactly what you're looking for, but git-annex has > code to use > tahoe as a 'special remote' > > https://git-annex.branchable.com/special_remotes/tahoe/ > > On Thursday 22 Oct 2015 22:18:57 Jean-Rene David wrote: > > Hello, > > > > I would like to use tahoe as a storage for my > > personal git repositories. The idea would be to > > have a local git repo for live work, and a > > tahoe-based bare remote where I could push my work > > and clone from. > > > > From the little I understand of tahoe, this could > > be a viable use-case since most files in a git > > repo are small and unmutable. > > > > The problem I would like to solve is how to get > > git to write its objects to tahoe. Is sshfs my > > only option? I read that this may not be entirely > > reliable. > > > > Are there other options? I'm perfectly willing to > > write some code. But I'm not sure where to start. > > > > Thanks, > _______________________________________________ > tahoe-dev mailing list > [email protected] > https://tahoe-lafs.org/cgi-bin/mailman/listinfo/tahoe-dev _______________________________________________ tahoe-dev mailing list [email protected] https://tahoe-lafs.org/cgi-bin/mailman/listinfo/tahoe-dev
