GIT server about js-git

[creationix]

Thanks for writing this up. I very much value use cases to know which direction to prioritize. This can be milestone #4 if that's soon enough (a few months out). Right now I'm working super hard to finish milestone #1 since that alone will be enough for many people's use cases. A large part of this work is creating packfiles which is currently part of milestone #2.

One comment on ssh. It's probably best to reuse the existing ssh server in servers. That's how real git works. What I would be re-implementing is the various shell commands that get spawned. These mini processes would then need to connect to the main git server process and talk to it on the client's behalf.

Now it would be more efficient if node was also also the ssh server and only understood git commands. But then your server wouldn't have an ssh server for remote logins anymore (unless node handled that too).

Also I would like to keep a js-git powered client as a separate task as a js-git powered server. Your use case may require both ends to be node powered, but many others do not.

[mattapperson]

My use case right now just requires js-git on the server... I would rather the client be able to use regular GIT.

SSH makes sense, I just wanted to point out the need for it.

Milestone 4 works... the sooner the better, but at the end of the day I understand the need to wait till milestone #4

[creationix]

I have a sample js-git server I'm using to develop the server-side of js-git. I just finished a basic version of repo.receivePack that allows you to push to js-git powered servers!
https://github.com/creationix/js-git/blob/master/examples/serve.js

It's still missing the protocol "report-status" extension that will be needed for post-commit hooks though.