@@ -1,12 +1,17 @@ --# title: Setting up a new remote git repository --# published: 2007-12-05 --# updated: 2008-01-09 - -:textile +-# title: Setting up a new remote git repository +-# published: 2007-12-05 +-# updated: 2008-01-09 + +:textile To collaborate in a distributed development process you'll need to push code to remotely accessible repositories. - + This is somewhat of a follow-up to the previous article "setting up a new rails app with git":http://toolmantim.com/article/2007/12/5/setting_up_a_new_rails_app_with_git. - + +.github-ad + :markdown + It's good to know how this stuff works, but this is definitely the hard way. For no fuss git repository setup (especially if you want to collaborate with others) check out [GitHub](http://github.com/?ref=toolmantim). + +:textile h2. For the impatient Set up the new bare repo on the server: @@ -227,125 +232,129 @@ h2. Further Reading - "Sourcemage's Git Guide":http://wiki.sourcemage.org/Git_Guide has some very very handy real-life examples of git commands you'll often need. - -#archived-comments - %h1 Archived comments - %p Comments were previously allowed on articles. Though no new comments are being accepted you can see the old comments below. - %ol - %li#comment_1384 - %p.author - Michael Koukoullis - .body - :textile - Okay now your making this stuff too easy ;) No more guesswork. Thanks for the post dude. - %li#comment_1388 - %p.author - %a{:href => 'http://saimonmoore.net'} Saimon Moore - .body - :textile + "Sourcemage's Git Guide":http://wiki.sourcemage.org/Git_Guide has some very very handy real-life examples of git commands you'll often need. + +.github-ad + :markdown + So now you know the hard way. For no fuss Git repository setup (especially if you want to collaborate with others) check out [GitHub](http://github.com/?ref=toolmantim). + +#archived-comments + %h1 Archived comments + %p Comments were previously allowed on articles. Though no new comments are being accepted you can see the old comments below. + %ol + %li#comment_1384 + %p.author + Michael Koukoullis + .body + :textile + Okay now your making this stuff too easy ;) No more guesswork. Thanks for the post dude. + %li#comment_1388 + %p.author + %a{:href => 'http://saimonmoore.net'} Saimon Moore + .body + :textile Tim, - Have you seen <a href="http://scie.nti.st/2007/11/14/hosting-git-repositories-the-easy-and-secure-way">gitosis</a> ? - %li#comment_1389 - %p.author - %a{:href => 'http://toolmantim.com'} Tim Lucas - .body - :textile + Have you seen <a href="http://scie.nti.st/2007/11/14/hosting-git-repositories-the-easy-and-secure-way">gitosis</a> ? + %li#comment_1389 + %p.author + %a{:href => 'http://toolmantim.com'} Tim Lucas + .body + :textile Michael: no problemo! ;) - Saimon: ah good idea to point out <a href="http://eagain.net/gitweb/?p=gitosis.git">gitosis</a>. It's a pretty kick-ass way to manage public git repositories. It's probably a good idea though to know how to set up remote git repositories manually, especially as gitosis is still under heavy development. - %li#comment_1390 - %p.author - %a{:href => 'http://toolmantim.com'} Tim Lucas - .body - :textile - Saimon: also I haven't actually tried gitosis yet, though I know <a href="http://drnicwilliams.com/">Dr Nic</a> had it up-and-running at railscamp and was yelling drunken praise - %li#comment_1400 - %p.author - %a{:href => 'http://mega.blaix.com/'} Justin - .body - :textile - Super simple. I had no idea. I'm inching ever-closer to trying out git for myself... - %li#comment_1416 - %p.author - Nico - .body - :textile - There's a minor bug in your instructions, I followed them to the letter and they did not work. You apparently cannot fetch from an empty repository, you have to push something into it first. In other words, your 'push' instructions should have come before your 'fetch' instructions. - %li#comment_1418 - %p.author - %a{:href => 'http://toolmantim.com'} Tim Lucas - .body - :textile - Nico: thanks you're right. I've restructed the entire article so it's now correct, as well as fleshing out how to interact with remote repositories. - %li#comment_1448 - %p.author - Chris - .body - :textile - Wow, thanks a bunch. This was helpful. - %li#comment_1454 - %p.author - %a{:href => 'http://www.bensblog.com'} Ben Poweski - .body - :textile + Saimon: ah good idea to point out <a href="http://eagain.net/gitweb/?p=gitosis.git">gitosis</a>. It's a pretty kick-ass way to manage public git repositories. It's probably a good idea though to know how to set up remote git repositories manually, especially as gitosis is still under heavy development. + %li#comment_1390 + %p.author + %a{:href => 'http://toolmantim.com'} Tim Lucas + .body + :textile + Saimon: also I haven't actually tried gitosis yet, though I know <a href="http://drnicwilliams.com/">Dr Nic</a> had it up-and-running at railscamp and was yelling drunken praise + %li#comment_1400 + %p.author + %a{:href => 'http://mega.blaix.com/'} Justin + .body + :textile + Super simple. I had no idea. I'm inching ever-closer to trying out git for myself... + %li#comment_1416 + %p.author + Nico + .body + :textile + There's a minor bug in your instructions, I followed them to the letter and they did not work. You apparently cannot fetch from an empty repository, you have to push something into it first. In other words, your 'push' instructions should have come before your 'fetch' instructions. + %li#comment_1418 + %p.author + %a{:href => 'http://toolmantim.com'} Tim Lucas + .body + :textile + Nico: thanks you're right. I've restructed the entire article so it's now correct, as well as fleshing out how to interact with remote repositories. + %li#comment_1448 + %p.author + Chris + .body + :textile + Wow, thanks a bunch. This was helpful. + %li#comment_1454 + %p.author + %a{:href => 'http://www.bensblog.com'} Ben Poweski + .body + :textile Excellent write up. - Thanks! - %li#comment_1468 - %p.author - %a{:href => 'http://www.exceptionz.com'} Maruis Marais - .body - :textile - Do you know how to create a bare repo without ssh'ing to the remote server? I'm trying to write a cap task to automate this process... - %li#comment_1474 - %p.author - %a{:href => 'http://www.seanhodges.co.uk/~sean/medes'} Sean - .body - :textile - Hey thanks for the article, very useful. Bookmarked for safe keeping! :) - %li#comment_1478 - %p.author - rxKaffee - .body - :textile + Thanks! + %li#comment_1468 + %p.author + %a{:href => 'http://www.exceptionz.com'} Maruis Marais + .body + :textile + Do you know how to create a bare repo without ssh'ing to the remote server? I'm trying to write a cap task to automate this process... + %li#comment_1474 + %p.author + %a{:href => 'http://www.seanhodges.co.uk/~sean/medes'} Sean + .body + :textile + Hey thanks for the article, very useful. Bookmarked for safe keeping! :) + %li#comment_1478 + %p.author + rxKaffee + .body + :textile M. Marais. Unless your remote shell is setup as the limited git-sh, you should be able to run a remote command over non-interactive ssh from your automation script. Something along the lines of ... - ssh gituser@myserver.com "REP=code.git; mkdir $REP; cd $REP; git --bare init;" - %li#comment_1503 - %p.author - Wladimir - .body - :textile - Thank you very much, using git is still like talking Chinese to me sometimes, but articles like this help a lot if I actually want to get stuff done :) - %li#comment_1508 - %p.author - walter - .body - :textile - any idea how to add the ssh port number during git remote add origin, and, git push origin branchname? Tried -p port : etc - %li#comment_1510 - %p.author - %a{:href => 'http://ahri.net'} Adam - .body - :textile + ssh gituser@myserver.com "REP=code.git; mkdir $REP; cd $REP; git --bare init;" + %li#comment_1503 + %p.author + Wladimir + .body + :textile + Thank you very much, using git is still like talking Chinese to me sometimes, but articles like this help a lot if I actually want to get stuff done :) + %li#comment_1508 + %p.author + walter + .body + :textile + any idea how to add the ssh port number during git remote add origin, and, git push origin branchname? Tried -p port : etc + %li#comment_1510 + %p.author + %a{:href => 'http://ahri.net'} Adam + .body + :textile walter: you can specify port as usual in the URL; ssh://foo.com:9999/foo.git - Tim: thanks a bunch for this guide, I'm really starting to enjoy using git and this is an invaluable quick reference! - %li#comment_1516 - %p.author - %a{:href => 'http://letshead.to'} Jagtesh Chadha - .body - :textile - It was very helpful! Thank you Tim :-) - %li#comment_1517 - %p.author - steve c - .body - :textile + Tim: thanks a bunch for this guide, I'm really starting to enjoy using git and this is an invaluable quick reference! + %li#comment_1516 + %p.author + %a{:href => 'http://letshead.to'} Jagtesh Chadha + .body + :textile + It was very helpful! Thank you Tim :-) + %li#comment_1517 + %p.author + steve c + .body + :textile Hey, don't know if you can help with this but when I do the push command I get this: (I have to C-c to stop it, it just "hangs") $ git push origin master @@ -353,71 +362,71 @@ Writing objects: 100% (3/3), 208 bytes, done. Total 3 (delta 0), reused 0 (delta 0) - I know it's connecting fine, if I change the remote origin to something that is not a git repo it errors out, I just don't know how to change this >.> - %li#comment_1521 - %p.author - %a{:href => 'http://droid.lv'} Arturs Aboltins - .body - :textile - Very helpful article. Explanation what goes in config files helped me a lot. Thanks! Good luck to you. - %li#comment_1522 - %p.author - %a{:href => 'http://abhibera.googlepages.com'} Abhijit Bera - .body - :textile - Fantastic tutorial! Definitely the best guide I have come across. Even a first timer can follow this. - %li#comment_1528 - %p.author - %a{:href => 'http://github.com/sr'} sr - .body - :textile - I wrote a bash function to automate the process. http://gist.github.com/7531 - %li#comment_1529 - %p.author - %a{:href => 'http://blog.infinitered.com'} Todd Werth - .body - :textile - Many thanks; well written and very helpful. - %li#comment_1532 - %p.author - %a{:href => 'http://effectif.com'} Graham Ashton - .body - :textile - Cracking post - just what I was looking for, thanks. - %li#comment_1533 - %p.author - %a{:href => 'http://www.hvmsolutions.co.in'} Gujjugeek - .body - :textile - Really helpful for a git novice like me. I spent majority of y'day trying to figure out a way to work with branches. didn't know it was so simple! thanks again. - %li#comment_1534 - %p.author - %a{:href => 'http://catalyst.net.nz'} dekita - .body - :textile - This guide does a great job of covering the essential features of day to day git usage. Thanks! - %li#comment_1535 - %p.author - %a{:href => 'http://www.markmcb.com'} Mark McBride - .body - :textile - Tim, great article! I <a href="http://markmcb.com/2008/09/17/migrating-a-subversion-svn-project-and-server-to-git/">cited you</a> in an article I wrote specific moving Rails apps from Subversion. One thing that stumped me when following your guide was how to push back to a remote branch that had been checked out locally and given a different name. I threw up some notes on my blog about <a href="http://markmcb.com/2008/09/21/multiple-remote-git-branches-with-different-local-names/">how to git push to a remote branch with a name that doesn't match the local branch name</a>. I how it helps other trying to do the same. - %li#comment_1551 - %p.author - %a{:href => 'http://thelucid.com'} Jamie Hill - .body - :textile + I know it's connecting fine, if I change the remote origin to something that is not a git repo it errors out, I just don't know how to change this >.> + %li#comment_1521 + %p.author + %a{:href => 'http://droid.lv'} Arturs Aboltins + .body + :textile + Very helpful article. Explanation what goes in config files helped me a lot. Thanks! Good luck to you. + %li#comment_1522 + %p.author + %a{:href => 'http://abhibera.googlepages.com'} Abhijit Bera + .body + :textile + Fantastic tutorial! Definitely the best guide I have come across. Even a first timer can follow this. + %li#comment_1528 + %p.author + %a{:href => 'http://github.com/sr'} sr + .body + :textile + I wrote a bash function to automate the process. http://gist.github.com/7531 + %li#comment_1529 + %p.author + %a{:href => 'http://blog.infinitered.com'} Todd Werth + .body + :textile + Many thanks; well written and very helpful. + %li#comment_1532 + %p.author + %a{:href => 'http://effectif.com'} Graham Ashton + .body + :textile + Cracking post - just what I was looking for, thanks. + %li#comment_1533 + %p.author + %a{:href => 'http://www.hvmsolutions.co.in'} Gujjugeek + .body + :textile + Really helpful for a git novice like me. I spent majority of y'day trying to figure out a way to work with branches. didn't know it was so simple! thanks again. + %li#comment_1534 + %p.author + %a{:href => 'http://catalyst.net.nz'} dekita + .body + :textile + This guide does a great job of covering the essential features of day to day git usage. Thanks! + %li#comment_1535 + %p.author + %a{:href => 'http://www.markmcb.com'} Mark McBride + .body + :textile + Tim, great article! I <a href="http://markmcb.com/2008/09/17/migrating-a-subversion-svn-project-and-server-to-git/">cited you</a> in an article I wrote specific moving Rails apps from Subversion. One thing that stumped me when following your guide was how to push back to a remote branch that had been checked out locally and given a different name. I threw up some notes on my blog about <a href="http://markmcb.com/2008/09/21/multiple-remote-git-branches-with-different-local-names/">how to git push to a remote branch with a name that doesn't match the local branch name</a>. I how it helps other trying to do the same. + %li#comment_1551 + %p.author + %a{:href => 'http://thelucid.com'} Jamie Hill + .body + :textile Instead of editing the config file manually to add the origin server, you could run: git-config branch.master.remote origin git-config branch.master.merge refs/heads/master - I have a fear of manually editing anything in the actual repository :) - %li#comment_1559 - %p.author - Gabriel - .body - :textile + I have a fear of manually editing anything in the actual repository :) + %li#comment_1559 + %p.author + Gabriel + .body + :textile Thanks a lot for the post, it was helpful. I was trying to setup a public repo that people could get at via http - and to do that, you need to do two more commands on the remote repo: @@ -428,12 +437,12 @@ (the second command didn't work for me - the hook was already in the right place) This is from the git documentation: - http://www.kernel.org/pub/software/scm/git/docs/user-manual.html#public-repositories - %li#comment_1560 - %p.author - Gabriel - .body - :textile + http://www.kernel.org/pub/software/scm/git/docs/user-manual.html#public-repositories + %li#comment_1560 + %p.author + Gabriel + .body + :textile One addendum to my prior comment: you need to mark the post-update hook as executable: - chmod +x hooks/post-update + chmod +x hooks/post-update articles/setting_up_a_new_remote_git_repository.haml @@ -57,3 +57,11 @@ $(function() { navigator.fadeIn(1000); }); }); + +// Github ads +$(function() { + $(".github-ad a").click(function() { + pageTracker._trackPageview('/outgoing/github.com'); + return true; + }); +}) \ No newline at end of file public/javascripts/all.js @@ -395,6 +395,11 @@ body.projects p.page-desc li :font-size 1.0em + .github-ad + :border-left 4px solid #666 + :padding-left 10px + :color #fff + @import views/stylesheets/code_highlighting.sass body.projects views/stylesheets/screen.sass 86b2d7e0929d561b123b4f334554eb6eb26e880c Tim Lucas t.lucas@toolmantim.com http://github.com/toolmantim/toolmantim/commit/e18fdb1cfa0542f47e8d3f095dd343a67d35acd8 e18fdb1cfa0542f47e8d3f095dd343a67d35acd8

2009-06-28T05:12:33-07:00

Tweakage e5f7394e9be8f2da3680b00c4212c7773b650dd2 Tim Lucas t.lucas@toolmantim.com