Tahoe as git remote

[Daira Hopwood]

On 26/10/15 10:55, Jean-Rene David wrote:
> * Greg Troxel [2015.10.23 09:21]:
>>
>> Jean-Rene David <tahoe-dev at levelnine.net> writes:
>>
>>> 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. 
>>
>> I see two reasonable ways forward.  One is to test and/or debug the
>> sshfs approach, and perhaps finish how authentication is handled.  It
>> would be reasonable to run filesystem tests on it.
>>
>> The other is to implement a FUSE interface for tahoe.
> 
> Actually the reason I wanted to use tahoe as a
> remote only was to avoid going the filesystem
> route. There is a protocol to talk to remotes and
> it's completely different (and hopefully simpler)
> than implementing a filesystem layer.

+1. It's also more likely to be correct, due to the complexity of
filesystem protocols and their semantic mismatch with Tahoe-LAFS.
Please feel free to open a ticket about adding a git remote implementation,
and ask for help with any more specific problems you run into.

-- 
Daira Hopwood  ⚧Ⓐ

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 490 bytes
Desc: OpenPGP digital signature
URL: <http://tahoe-lafs.org/pipermail/tahoe-dev/attachments/20151026/c9bddb10/attachment.pgp>