Sharing a public Git repo over HTTP [flow chart] March 11, 2008
There is also an SVG version of this flow, which is more readable (but poor IE folks will have issues). Notes: This is a simplest possible configuration. Be sure to check out the docs for git-remote to see how to, optionally, designate specific local or remote branches. Many of the initial commands could be performed locally and then just uploaded to the server. This particular sequence guarantees that all the connection pieces are in place and working correctly.
Much thanks to Tim Toolman for getting this info into two easy to follow posts: Sharing git repositories via OS X’s built-in web sharing and Setting up a new remote git repository. However, this doesn’t feel elegant to me. If anyone can come up with a simpler / more elegant way to do this please add a comment.
This image is copyright 2008 Very Useful Books, Inc. and is distributed under the GPL v2. It was created with OmniGraffle 4. If anyone wants the original, just holler.
Popularity: 14% [?]
What software do you use to create your flow charts? They are very attractive. Thanks for the great articles,
Andrew
this is not public http, this is ssh, rather private by nature
um… NO. the pushing is private the SHARING with the rest of the world is VERY public. With Git you don’t need to give everyone write access to the repo. They can write to their own copy of it and send in patches or ask the maintainers to pull from them. Note the “where the web server can share it” annotation.
[…] weblog.masukomi.org » Sharing a public Git repo over HTTP [flow chart] (tags: scm) […]
If git repository already exists on your machine when you are configuring your public server, instead of “git –bare init” on public side + “git push” on local side you can (if your local machine is visible from public server, e.g. via ssh) you can do “git clone –bare “.
If you cannot login on local machine from server, I agree that the above diagram is best solution.