Sharing a public Darcs repo over HTTP [flow chart] March 11, 2008
The same friend who wondered about how to share a Git repo over HTTP dared to suggest that “It’s so easy with Hg…”. While I happen to disagree that it’s easier in Hg than Git, I think this flow chart successfully demonstrates that, on this front, Hg and Git both suck ass when compared to Darcs.
P.S. Yes, while 100% factual, the graph is also intentionally silly.
[update] After considering it more I think think it probably is easier to share a repo with Hg than Git, but I dislike the fact that it involves mucking about with things outside of the repo. You have to set up a CGI. You have to alter a config file that tells it what repos to share and where…. Yes, there’s a built in server you could use but that’s really an edge case. Most of the time you’ll want to leverage an existing web server.
This flowchart works for git too. If you copy a git repo up to your server, you can immediately clone it:
scp -r my-git-project me@example.com:
cd /tmp
git clone http://example.com/my-git-project/.git
I don’t see how that’s any harder than Darcs…?
The problem with that is that you can’t push to it. Unless you’re working with a bare repo Git will accept your pushes but it won’t commit them. Or, that’s my understanding of it. Yes, you could just keep re-uploading, and over-writing the repo on the server but that seems a crude work-around.
Amusing. I love it!
Mark