Shameless plug: Might be interesting to combine this with client-side encrypted remotes, a feature of https://github.com/lucas-clemente/git-cr :)
Gitfs
11–20 of 34 posts
Re: Gitfs
#12For write support you obviously have to mount a branch. Can you mount tags or commits read-only? It would be really useful actually. Actually I can't see a use case where I would mount it read-write. For developing a website you possibly do not want to commit on every write. Possibly git's limitations on large files still apply to this implementation. For large number of small files: what does it do when I cp like 10…
> mount -o ro ...
Since it is a fuse filesystem you don't mount it with mount but with the command gitfs (note that there is no single instruction on the main page how to mount, not even in the demo), then unmount with fusermount -u.
Re: Gitfs
#13There is a nice EuroPython talk were two of the authors talked about gitfs: https://ep2015.europython.eu/conference/talks/gitfs-building... Their main motivation to write this was to give their clients (publishers) a way to interact with a git-versioned project tree without having to force them to use git directly. Overall pretty amazing work!
Video here: https://www.youtube.com/watch?v=LEJb1VZxRoE
Re: Gitfs
#14"Merges with upstream by automatically accepting local changes"
For some reason, this scares me. Is there more info on that somewhere?
Re: Gitfs
#15OK, the main page lacks information.
https://www.presslabs.com/gitfs/docs/usage/
https://www.presslabs.com/gitfs/docs/arguments/
So apparently you can mount remotes, not only local .git dirs. This is really handy and it should be listed on the main page, really.
I raises an other question: can I mount remotes where I don't have write access read-only?
For the directory structure the history directory makes sense for mounted projects that are edited with gitfs. For other projects, not so much. What about having a read only tags/ and commits/ directory too?
Re: Gitfs
#16OK, the main page lacks information. https://www.presslabs.com/gitfs/docs/usage/ https://www.presslabs.com/gitfs/docs/arguments/ So apparently you can mount remotes, not only local .git dirs. This is really handy and it should be listed on the main page, really. I raises an other question: can I mount remotes where I don't have write access read-only? For the directory structure the history directory makes sense for…
I agree, the main page is a little bit outdated.
You can mount remotes with where you have only read access, gitfs will fail to push something on the remote, and will put the entire repository in read-only. Right now, you don't have a read-only option, but it would be nice to have :)
Great idea about tags and commits directories. It would be nice to specify at mount point, if you also want tags and/or commits etc.
You can fork it https://github.com/PressLabs/gitfs and start hacking around.
Re: Gitfs
#17This reminds me I haven't updated my Perl fuse interface to a Git repo in a long, long while… https://github.com/mfontani/git-fuse-perl
Re: Gitfs
#18interesting to see this! the first thing that came to mind was irmin, from the good folks at MirageOS. unikernels provide an interesting opportunity to rethink block storage, as you're no longer bound the rest of your operating system.
curious to see how gitfs and irmin develop.
Re: Gitfs
#19Python 2 only - disappointing.
Re: Gitfs
#20"Merges with upstream by automatically accepting local changes" For some reason, this scares me. Is there more info on that somewhere?
Yes, it can be scary, but usually this is the safest strategy. You can implement your own strategy and use it very easily (https://github.com/PressLabs/gitfs/tree/master/gitfs/merges).
Also, you can see how conflicts are solved, directly in the implementation (https://github.com/PressLabs/gitfs/blob/master/gitfs/merges/...).
Do you want to know something more specific?