{"thread":{"id":"35554","subject":"git fuse","startedAt":"2013-12-19T21:15:00Z","lastAt":"2013-12-25T23:01:12Z","messageCount":2,"participants":["Thomas Koch","Drew Northup"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"232263","messageId":"201312192215.01103.thomas@koch.ro","threadId":"35554","inReplyTo":null,"subject":"git fuse","fromName":"Thomas Koch","fromEmail":"thomas@koch.ro","sentAt":"2013-12-19T21:15:00Z","receivedAt":"2013-12-19T21:15:00Z","isPatch":false,"sender":{"key":"thomas@koch.ro","avatar":null},"body":"Hi,\n\nI'm thinking about using Git for web application deployment and thought that I \nwouldn't even need to checkout a worktree if I could access the bare git repo \nvia fuse.\n\nWhat would be the performance impact? Once the files are in the filesystem cache \nit shouldn't matter anymore, how fast the git fuse layer is, should it?\n\nDo you know any active and stable git-fuse project? \n\na) https://github.com/davesque/gitfuse\nPython, last  commit 1 year ago\n\nb) https://github.com/mfontani/git-fuse-perl\nPerl, last commit 3 years ago\n\nc) \nhttp://www.seas.upenn.edu/~cse400/CSE400_2008_2009/websites/grant/project.html\nhttp://repo.or.cz/w/figfs.git\nthesis, OCaml, last touched in 2009\n\nd) https://github.com/rossbiro/GitFS\nPython, recent but declared pre-alpha\n\ne) https://github.com/patrickhaller/git-fs\nC, last commit 2 years ago\n\nf) https://github.com/wereHamster/gitfs\nhttps://blog.caurea.org/2009/07/22/having-fun-with-gitfs.html\nC, last commit 2 years ago\n\nRegards,\n\nThomas Koch2\n"},{"id":"232391","messageId":"CAM9Z-nmVaBDcRABMRJGLdFVDSLRGL31jMS9KpaWiQ4y_SYONdg@mail.gmail.com","threadId":"35554","inReplyTo":"201312192215.01103.thomas@koch.ro","subject":"Re: git fuse","fromName":"Drew Northup","fromEmail":"n1xim.email@gmail.com","sentAt":"2013-12-25T23:01:12Z","receivedAt":"2013-12-25T23:01:12Z","isPatch":false,"sender":{"key":"n1xim.email@gmail.com","avatar":null},"body":"On Thu, Dec 19, 2013 at 4:15 PM, Thomas Koch <thomas@koch.ro> wrote:\n> Hi,\n>\n> I'm thinking about using Git for web application deployment and thought that I\n> wouldn't even need to checkout a worktree if I could access the bare git repo\n> via fuse.\n\nThomas,\nGiven that gitweb (and more than a few other similar tools) doesn't\nuse FUSE and works on bare repositories I question why you think you'd\nneed (or want) to introduce the additional layer.\n\n> What would be the performance impact? Once the files are in the filesystem cache\n> it shouldn't matter anymore, how fast the git fuse layer is, should it?\n\nIf your concern is caching, it should be implemented upon already\nrendered / prepared objects whenever possible--frequently not a file\nsystem level implementation. This is a design concern that has no\nspecific requirement whatsoever to do with FUSE (or for that matter,\nwith most of the VFS layer when accessing raw disk--as VFS itself is\nhighly optimized already).\n\nI am not qualified to answer questions about FUSE use of the VFS cache.\n\nI would strongly consider using a tool such as Varnish if you are\nconcerned about performance when serving static or semi-static content\n(may it reside in a Git repo or elsewhere). The architectural concerns\nof your web-app should probably guide your design in this sort of\ndirection anyway if it will be expected to sustain notable throughput\nover time.\n\nI hope that helps.\n\n(If you want to discuss this further it would be worth considering if\nyour questions are Git questions or web-app design questions. The\nlatter should be taken elsewhere.)\n\n-- \n-Drew Northup\n--------------------------------------------------------------\n\"As opposed to vegetable or mineral error?\"\n-John Pescatore, SANS NewsBites Vol. 12 Num. 59\n"}]}