git-http-backend

[billiegoose]

I've been critical of the server-side design of git in the past and thought I could design a better one... but honestly the simplicity of the CGI design has grown on me. I think the easiest way to get isomorphic-git into the server is to just straight up implement git-http-backend. Let it go ahead and parse URLs - instead of a dir/gitdir argument like normal we'd have a gitProjectRoot dir and combine it with the path. We can break git-http-backend down into individual git-upload-pack and git-receive-pack services and expose more granular functionality later if needed.

[juancampa]

For what is worth, this is the implementation I've been using: https://github.com/substack/git-http-backend (2 years old)

[juancampa]

Whoa, I just saw what you're up to with WebSocket support and everything. Really excited!

[billiegoose]

I've been using substack's git-http-backend in this project: https://github.com/isomorphic-git/git-http-mock-server It's really great, and one of the reason's I've decided to directly implement git-upload-pack and git-receive-pack rather than design my own server functions is so I can easily swap in the isomorphic-git versions without having to change the code much.

[robert-cronin]

Has there been any progress on implementing git-upload-pack and git-receive-pack? Alternatively is there any other way to serve a git repo directly from isomorphic-git? This would be a great feature as it would allow one to byo fs and not rely on node to serve git repos. I am particularly looking at using a virtual file system to serve git repos.