-
Notifications
You must be signed in to change notification settings - Fork 77
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Serve bare git repo from a remote server? #54
Comments
I would like to know the answer to this too. Bonus points for proxying to another git server like GitHub itself! |
I am facing this problem too, i want to host all my repos to s3 instead of my own server and clone them using the same method. |
@gabrielcsapo Please could u help or can guide us ? |
+1, this would be super nice (I could also contribute if needed) |
This question is quite old, but having spent a little time in the node-git-server code, I think the answer to this is not easily. This package calls git on the host's operating system like so: node-git-server/lib/service.js Lines 107 to 112 in 5279f64
Converting that to instead using streams and pulling from remote hosts would, in my opinion, be a lot of work. Also, if you check the philosophy section of this package, it aims to have zero dependencies. Adding streaming from remote hosts would definitely require dependencies. |
Hello, firstly - thanks for the amazing repo.
I understand that in your implementation (and stackdot's), you use
git-upload-pack
andgit-receive-pack
processes to allow the client and server to talk to each other (figure out what packets the other needs, etc.) To my knowledge, this git command accepts a local directory, but what if I host all my bare git repositories on a separate server, like an AWS S3 bucket? Could I stream a remote bare repo to these git commands, that then stream the necessary packets to the client? I don't want to host all my bare git repos on my heroku instance, since the storage is ephemeral and limited. Any guidance would be appreciated!The text was updated successfully, but these errors were encountered: