# Anybody home? 20 messages from 2011-09-15 to 2011-09-15. Participants: Joshua Stoutenburg, Michael Witten, Alexander Kostikov, Johannes Sixt, Thomas Rast, Carlos Martín Nieto, Miles Bader, Jakub Narebski, Ted Ts'o, Martin Langhoff, Scott Chacon. Thread: https://gitlist.dev/t/28394 ## Joshua Stoutenburg, 2011-09-15 04:24 Subject: Anybody home? Message-ID: URL: https://gitlist.dev/e/CAOZxsTq1crC0zeMpFGMafG8HXu168gkK2-KDnpwLoamRLJshjg%40mail.gmail.com ``` Hey guys, I'm pretty stoked about git -- coming from subversion. I'm having a hard time understanding clearly how to set up a git server and configure my local machine to pull and push to it. I've been reading the git book pdf. But I think I must have missed something. I feel stranded. Any help appreciated. Many thanks. -- Josh ``` ## Michael Witten, 2011-09-15 04:48 Subject: Re: Anybody home? Message-ID: URL: https://gitlist.dev/e/CAMOZ1BtpzsxGLzrZs2YbNP174mm3vfLCteencKSepDR329jjBQ%40mail.gmail.com In-Reply-To: ``` On Thu, Sep 15, 2011 at 04:24, Joshua Stoutenburg wrote: > Hey guys, I'm pretty stoked about git -- coming from subversion. > > I'm having a hard time understanding clearly how to set up a git > server and configure my local machine to pull and push to it. > > I've been reading the git book pdf.  But I think I must have missed > something.  I feel stranded. > > Any help appreciated.  Many thanks. Could you please ask a specific question about a specific issue of confusion? ``` ## Joshua Stoutenburg, 2011-09-15 05:04 Subject: Re: Anybody home? Message-ID: URL: https://gitlist.dev/e/CAOZxsTrsi5mNdm8OgvfXyYwj1T4Vw3HfQGN-5Dsb%2BQnX0nz4ag%40mail.gmail.com In-Reply-To: ``` On Wed, Sep 14, 2011 at 9:48 PM, Michael Witten wrote: > On Thu, Sep 15, 2011 at 04:24, Joshua Stoutenburg wrote: >> Hey guys, I'm pretty stoked about git -- coming from subversion. >> >> I'm having a hard time understanding clearly how to set up a git >> server and configure my local machine to pull and push to it. >> >> I've been reading the git book pdf.  But I think I must have missed >> something.  I feel stranded. >> >> Any help appreciated.  Many thanks. > > Could you please ask a specific question about a specific issue of confusion? > There seems to be a plethora of documentation on git from various sources. See what I mean: http://git-scm.com/documentation http://progit.org/book/ http://gitref.org/ http://www.kernel.org/pub/software/scm/git/docs/gittutorial.html http://www.kernel.org/pub/software/scm/git/docs/everyday.html http://git-scm.com/course/svn.html http://hoth.entp.com/output/git_for_designers.html http://eagain.net/articles/git-for-computer-scientists/ http://www.kernel.org/pub/software/scm/git/docs/user-manual.html http://www-cs-students.stanford.edu/~blynn/gitmagic/ http://help.github.com/ http://www.kernel.org/pub/software/scm/git/docs/ http://refcardz.dzone.com/refcardz/getting-started-git Which source makes the least amount of assumptions and offers all the juicy details for configuring git on the server, and git on the local machine, without any fluff? I'm looking for a solid guide. Not a novel. Not a pamphlet. Being new to git, I can't tell which source to go with. Perhaps someone with greater experience could point me in the right direction. Thanks again. --Josh ``` ## Joshua Stoutenburg, 2011-09-15 05:06 Subject: Re: Anybody home? Message-ID: URL: https://gitlist.dev/e/CAOZxsTr%2BmC9cajGa21d1sqKBEB%2BsUhsBOHoTuVj1D%2B6uTFTL6g%40mail.gmail.com In-Reply-To: ``` Also, I noticed the entire kernel.org website is down. Any idea how long it's been like that or when/if it will come back up? What's Linus up to? ``` ## Alexander Kostikov, 2011-09-15 05:21 Subject: Re: Anybody home? Message-ID: URL: https://gitlist.dev/e/CAGAhT3%3Dwak7qrcmXfTXWyQnb_%2BiWOt24baVUH9de%3DrrUHwrWgQ%40mail.gmail.com In-Reply-To: ``` If you don't mind spending $12 on documentation here is IMHO very good guide to git - http://peepcode.com/products/git-internals-pdf It contains some videos as well. On Wed, Sep 14, 2011 at 10:06 PM, Joshua Stoutenburg wrote: > > Also, I noticed the entire kernel.org website is down.  Any idea how > long it's been like that or when/if it will come back up?  What's > Linus up to? > -- > To unsubscribe from this list: send the line "unsubscribe git" in > the body of a message to majordomo@vger.kernel.org > More majordomo info at  http://vger.kernel.org/majordomo-info.html -- Alexander Kostikov ``` ## Joshua Stoutenburg, 2011-09-15 05:37 Subject: Re: Anybody home? Message-ID: URL: https://gitlist.dev/e/CAOZxsTq%2B9HuCDgTyj%3D3KQdbgPbqmZbvf_6jCp4e%3Dn6ig_aZRrw%40mail.gmail.com In-Reply-To: ``` On Wed, Sep 14, 2011 at 10:19 PM, Alexander Kostikov wrote: > If you don't mind spending $12 on documentation here is IMHO very good guide > to git - http://peepcode.com/products/git-internals-pdf > It contains some videos as well. I'll definitely check it out. Not really looking for videos though. I like things that are quiet, skim-able, and searchable. ``` ## Johannes Sixt, 2011-09-15 07:15 Subject: Re: Anybody home? Message-ID: <4E71A5FF.5040807@viscovery.net> URL: https://gitlist.dev/e/4E71A5FF.5040807%40viscovery.net In-Reply-To: ``` Am 9/15/2011 6:24, schrieb Joshua Stoutenburg: > Hey guys, I'm pretty stoked about git -- coming from subversion. > > I'm having a hard time understanding clearly how to set up a git > server and configure my local machine to pull and push to it. > > I've been reading the git book pdf. But I think I must have missed > something. I feel stranded. Reading your exchanges elsewhere in this thread, I think you missed that you don't need a git server at all just to *use* git. Even when you want to exchange your commits between two or three machines, all you need is ssh access. There is no *git server* necessary. git is not svn. ;-) I thought I'd just mention this to help you streamline your search. -- Hannes ``` ## Thomas Rast, 2011-09-15 07:48 Subject: Re: Anybody home? Message-ID: <201109150948.09040.trast@student.ethz.ch> URL: https://gitlist.dev/e/201109150948.09040.trast%40student.ethz.ch In-Reply-To: <4E71A5FF.5040807@viscovery.net> ``` Johannes Sixt wrote: > Even when you want to exchange your commits between two or three machines, > all you need is ssh access. There is no *git server* necessary. git is not > svn. ;-) I'd even put this somewhat more bluntly. My two-step advice on switching from svn to git is: 1) forget *everything* you know from SVN 2) learn git as usual I don't hang out on IRC as much any more, so maybe it got better. But 90%[*] of SVN convert's problems seem to stem from some preconceived notions they carried over from SVN. Such as, "HEAD is the newest commit". Or the whole centralized vs. distributed you mentioned. [*] 78% of all statistics were made up on the spot -- Thomas Rast trast@{inf,student}.ethz.ch ``` ## Joshua Stoutenburg, 2011-09-15 09:01 Subject: Re: Anybody home? Message-ID: URL: https://gitlist.dev/e/CAOZxsTqGt%3DgYr3t7e5Ma4z6W9wt_JxrgsNSGFGVbtk2rc3LZ9w%40mail.gmail.com In-Reply-To: <4E71A5FF.5040807@viscovery.net> ``` > Reading your exchanges elsewhere in this thread, I think you missed that > you don't need a git server at all just to *use* git. > > Even when you want to exchange your commits between two or three machines, > all you need is ssh access. There is no *git server* necessary. git is not > svn. ;-) > > I thought I'd just mention this to help you streamline your search. > > -- Hannes > I read the first four and a half chapters from the Pro Git book pdf. So I think I understood that much. But in my situation, I do need a server so that other developers can access anytime over the internet. I should have mentioned that. ``` ## Joshua Stoutenburg, 2011-09-15 09:42 Subject: Re: Anybody home? Message-ID: URL: https://gitlist.dev/e/CAOZxsTrxPZ1V%2B_W%3DtrRpOTJ9emh8msreGOyAYm_1hs0zXaOd1w%40mail.gmail.com In-Reply-To: <201109150948.09040.trast@student.ethz.ch> ``` On Thu, Sep 15, 2011 at 12:48 AM, Thomas Rast wrote: > Johannes Sixt wrote: >> Even when you want to exchange your commits between two or three machines, >> all you need is ssh access. There is no *git server* necessary. git is not >> svn. ;-) > > I'd even put this somewhat more bluntly.  My two-step advice on > switching from svn to git is: > > 1) forget *everything* you know from SVN > 2) learn git as usual > > I don't hang out on IRC as much any more, so maybe it got better.  But > 90%[*] of SVN convert's problems seem to stem from some preconceived > notions they carried over from SVN. > > Such as, "HEAD is the newest commit".  Or the whole centralized > vs. distributed you mentioned. > > > > [*] 78% of all statistics were made up on the spot > > -- > Thomas Rast > trast@{inf,student}.ethz.ch > How can I "learn git as usual"? I don't think I was on Subversion long enough to permanently damage my brain. Only a few months (actually . . . that's probably enough). I never used it's branching, tagging or merging features. Commit and revert were the only that I used. Regardless, I'm happy to forget everything I know about Subversion. I've watched Linus Torvalds tech talk on git: http://www.youtube.com/watch?v=4XpnKHJAok8 I also read four and a half chapters of Pro Git pdf: http://progit.org/ebook/progit.pdf I read and understood git for computer scientists: http://eagain.net/articles/git-for-computer-scientists/ So I have a pretty good understanding why git is THE superior source code management choice. And I have a basic understanding of how git works. I know how to install a *nix server and can survive on the CLI. Here's where I think I'm having some troubles, and maybe you can help me identify any others: I got confused in Chapter 5 of the Pro Git pdf book, trying to discern what needs to be done on the server, and what needs to be done on the work station. The chapter seems to jump around a bit, and doesn't follow a linear pattern. Maybe I need to read it more carefully? Also, I'm not clear on the best way to manage large numbers of git users (like 12-24), who also may have permissions to other services as well (ftp, databases, email, etc). I have some hesitancy creating each one manually on the CLI. Finally, I'm not sure how to "learn git as usual". Point me in the right direction, please. ``` ## Carlos Martín Nieto, 2011-09-15 09:43 Subject: Re: Anybody home? Message-ID: <1316079837.2019.18.camel@bee.lab.cmartin.tk> URL: https://gitlist.dev/e/1316079837.2019.18.camel%40bee.lab.cmartin.tk In-Reply-To: ``` On Thu, 2011-09-15 at 02:01 -0700, Joshua Stoutenburg wrote: > > Reading your exchanges elsewhere in this thread, I think you missed that > > you don't need a git server at all just to *use* git. > > > > Even when you want to exchange your commits between two or three machines, > > all you need is ssh access. There is no *git server* necessary. git is not > > svn. ;-) > > > > I thought I'd just mention this to help you streamline your search. > > > > -- Hannes > > > > I read the first four and a half chapters from the Pro Git book pdf. > So I think I understood that much. > > But in my situation, I do need a server so that other developers can > access anytime over the internet. If the code shouldn't be made public, then you should take a look at gitolite[0]. Otherwise, you can just host it on gitorious.org or github.com [0] https://github.com/sitaramc/gitolite cmn > > I should have mentioned that. > -- > To unsubscribe from this list: send the line "unsubscribe git" in > the body of a message to majordomo@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html > ``` ## Joshua Stoutenburg, 2011-09-15 09:51 Subject: Re: Anybody home? Message-ID: URL: https://gitlist.dev/e/CAOZxsToO0n%2B9%2BxG64jKmQwNCQZ4%2BFyE-eHN-unJBK-X5EFRWiw%40mail.gmail.com In-Reply-To: <1316079837.2019.18.camel@bee.lab.cmartin.tk> ``` On Thu, Sep 15, 2011 at 2:43 AM, Carlos Martín Nieto wrote: > If the code shouldn't be made public, then you should take a look at > gitolite[0]. Otherwise, you can just host it on gitorious.org or > github.com > > [0] https://github.com/sitaramc/gitolite > >   cmn > Thank you. This looks very useful. ``` ## Miles Bader, 2011-09-15 10:54 Subject: Re: Anybody home? Message-ID: URL: https://gitlist.dev/e/buoty8e3wjq.fsf%40dhlpc061.dev.necel.com In-Reply-To: <1316079837.2019.18.camel@bee.lab.cmartin.tk> ``` Carlos Martín Nieto writes: > If the code shouldn't be made public, then you should take a look at > gitolite[0]. Otherwise, you can just host it on gitorious.org or > github.com Hmm, of course if you're willing to pay, github will also host private code (maybe useful if your devs love teh shiny......). -miles -- One of the lessons of history is that nothing is often a good thing to do, and always a clever thing to say. -- Will Durant ``` ## Jakub Narebski, 2011-09-15 11:04 Subject: Re: Anybody home? Message-ID: URL: https://gitlist.dev/e/m3y5xqrro0.fsf%40localhost.localdomain In-Reply-To: ``` Couldn't you pick up less descriptive subject ;-) ? Joshua Stoutenburg writes: > On Wed, Sep 14, 2011 at 9:48 PM, Michael Witten wrote: >> On Thu, Sep 15, 2011 at 04:24, Joshua Stoutenburg wrote: >>> I'm having a hard time understanding clearly how to set up a git >>> server and configure my local machine to pull and push to it. > There seems to be a plethora of documentation on git from various sources. > > See what I mean: > http://git-scm.com/documentation > http://progit.org/book/ > http://gitref.org/ > http://www.kernel.org/pub/software/scm/git/docs/gittutorial.html > http://www.kernel.org/pub/software/scm/git/docs/everyday.html > http://git-scm.com/course/svn.html > http://hoth.entp.com/output/git_for_designers.html > http://eagain.net/articles/git-for-computer-scientists/ > http://www.kernel.org/pub/software/scm/git/docs/user-manual.html > http://www-cs-students.stanford.edu/~blynn/gitmagic/ > http://help.github.com/ > http://www.kernel.org/pub/software/scm/git/docs/ > http://refcardz.dzone.com/refcardz/getting-started-git > > Which source makes the least amount of assumptions and offers all the > juicy details for configuring git on the server, and git on the local > machine, without any fluff? > > I'm looking for a solid guide. Not a novel. Not a pamphlet. I think that either "Pro Git" book, or "The Git Community Book" would be a best source to learn about setting-up git server. I think the simplest solution for git hosting management would be to use gitolite (there are other git repository management software: Gitosis, SCM Manager, Gitblit). If you want to host something like GitHub, there are open source solutions too: Gitorious, InDefero, Girocco + gitweb,... HTH -- Jakub Narębski ``` ## Carlos Martín Nieto, 2011-09-15 11:34 Subject: Re: Anybody home? Message-ID: <1316086486.2019.20.camel@bee.lab.cmartin.tk> URL: https://gitlist.dev/e/1316086486.2019.20.camel%40bee.lab.cmartin.tk In-Reply-To: ``` On Thu, 2011-09-15 at 19:54 +0900, Miles Bader wrote: > Carlos Martín Nieto writes: > > If the code shouldn't be made public, then you should take a look at > > gitolite[0]. Otherwise, you can just host it on gitorious.org or > > github.com > > Hmm, of course if you're willing to pay, github will also host private Indeed, if you give them a bit of money they'll take care of everything and you can have your private code there. > code (maybe useful if your devs love teh shiny......). Teh Shiny is powerful :) cmn ``` ## Joshua Stoutenburg, 2011-09-15 12:01 Subject: Re: Anybody home? Message-ID: URL: https://gitlist.dev/e/CAOZxsToPY4k4CTsqUxX5t6uTHZXbbTAG7Ty3TjxoeGgj3Jn2gA%40mail.gmail.com In-Reply-To: <1316086486.2019.20.camel@bee.lab.cmartin.tk> ``` On Thu, Sep 15, 2011 at 4:34 AM, Carlos Martín Nieto wrote: > On Thu, 2011-09-15 at 19:54 +0900, Miles Bader wrote: >> Carlos Martín Nieto writes: >> > If the code shouldn't be made public, then you should take a look at >> > gitolite[0]. Otherwise, you can just host it on gitorious.org or >> > github.com >> >> Hmm, of course if you're willing to pay, github will also host private > > Indeed, if you give them a bit of money they'll take care of everything > and you can have your private code there. > >> code (maybe useful if your devs love teh shiny......). > > Teh Shiny is powerful :) > >   cmn > > Unfamiliar with the term "Teh Shiny". Had to look it up. Found this: http://www.claassen.net/geek/blog/2009/09/teh-shiny.html I think I have a tendency to avoid "Teh Shiny" because it ruins all the fun. I think I could easily figure out how to host my own repos, save some money, and have my own "Teh Shiny". If I didn't care about saving money, and had a project that needed a repo immediately, I'd probably give in and pay a little. ``` ## Ted Ts'o, 2011-09-15 12:55 Subject: Re: Anybody home? Message-ID: <20110915125510.GF15782@thunk.org> URL: https://gitlist.dev/e/20110915125510.GF15782%40thunk.org In-Reply-To: ``` On Wed, Sep 14, 2011 at 10:06:58PM -0700, Joshua Stoutenburg wrote: > Also, I noticed the entire kernel.org website is down. Any idea how > long it's been like that or when/if it will come back up? What's > Linus up to? It's down for maintenance after a security breach. https://lwn.net/Articles/458099/ - Ted ``` ## Martin Langhoff, 2011-09-15 13:17 Subject: Re: Anybody home? Message-ID: URL: https://gitlist.dev/e/CACPiFC%2BgXYn8cu5dwdcbzT1RYmmbdPhFhdejbxJs9zY8C-F4cQ%40mail.gmail.com In-Reply-To: ``` On Thu, Sep 15, 2011 at 5:42 AM, Joshua Stoutenburg wrote: > I got confused in Chapter 5 of the Pro Git pdf book, trying to discern > what needs to be done on the server, and what needs to be done on the > work station OK - some hints: 1 - For private code, or public code where you value the service, you can use the commercial services out there, that's easy 2 - For public/foss code, with low/simple service expectations, you can get free hosting 3 - For a private setup... the normal thing is to use git over ssh, so the server should be reachable by your users, and your users need an ssh account. You will want to setup a group ("gituser") and create a directory ("/git") owned by that group, writable by the group, with sticky group mode. To create a new project repo, ssh into the server and say git --git-dir /git/fooproject init --shared . It will be empty -- on a user workstation create your first commit, and push it into the (so far empty) repo with git push git+ssh://hostname/git/fooproject master . On the server you can add a gitweb or cgit install for browsability. If you want to allow anonymous users to access your git repos in readonly mode, you can setup the git "service", with xinetd. That allows you to tell people "git clone git://hostname/fooproject" . Careful when configuring network services if the host is public, you don't want to serve git://host/etc/shadow :-) This is what most "git servers" do -- it works in your company network, it also works for a public FOSS project with anon readers and a handful of ssh-authenticated committers. (For a project using a more distributed model of one-developer-one-repo, you follow the same setup but perhaps make per-developer directories.) 4 - You _can_ do git over http, instead of ssh, but I suspect the setup is more involved. In any case, others will have to fill in. > Also, I'm not clear on the best way to manage large numbers of git > users (like 12-24), who also may have permissions to other services as > well (ftp, databases, email, etc).  I have some hesitancy creating > each one manually on the CLI. CLI is generally fine :-) if you contract a hosting server that gives you email/db/ftp and has a webbased admin UI, all you need "additional" is to ensure you can manage ssh accounts with ease. cheers, m --  martin.langhoff@gmail.com  martin@laptop.org -- Software Architect - OLPC  - ask interesting questions  - don't get distracted with shiny stuff  - working code first  - http://wiki.laptop.org/go/User:Martinlanghoff ``` ## Scott Chacon, 2011-09-15 15:04 Subject: Re: Anybody home? Message-ID: URL: https://gitlist.dev/e/CAP2yMaJcKnghtxxDNVYk%3D00KQ-ZOGEwACHRTU15tGnOuk3R4Hw%40mail.gmail.com In-Reply-To: ``` Hey, On Thu, Sep 15, 2011 at 2:01 AM, Joshua Stoutenburg wrote: >> Reading your exchanges elsewhere in this thread, I think you missed that >> you don't need a git server at all just to *use* git. >> >> Even when you want to exchange your commits between two or three machines, >> all you need is ssh access. There is no *git server* necessary. git is not >> svn. ;-) >> >> I thought I'd just mention this to help you streamline your search. >> >> -- Hannes >> > > I read the first four and a half chapters from the Pro Git book pdf. > So I think I understood that much. > > But in my situation, I do need a server so that other developers can > access anytime over the internet. > > I should have mentioned that. I guess I'm confused. The fourth chapter of the Pro Git book is entirely about setting up your own Git server, including basically step by step instructions on Gitolite and Gitosis, in addition to simply running your own ssh-based server plus gitweb. It is like 20 pages long - how is this not exactly what you're asking for? Scott ``` ## Joshua Stoutenburg, 2011-09-15 21:00 Subject: Re: Anybody home? Message-ID: URL: https://gitlist.dev/e/CAOZxsTq0qMB_Y97WcodVbO6DmXRXBpP_at3SF-VkPbbcnDfjgw%40mail.gmail.com In-Reply-To: ``` On Thu, Sep 15, 2011 at 8:04 AM, Scott Chacon wrote: > Hey, > > On Thu, Sep 15, 2011 at 2:01 AM, Joshua Stoutenburg > wrote: >>> Reading your exchanges elsewhere in this thread, I think you missed that >>> you don't need a git server at all just to *use* git. >>> >>> Even when you want to exchange your commits between two or three machines, >>> all you need is ssh access. There is no *git server* necessary. git is not >>> svn. ;-) >>> >>> I thought I'd just mention this to help you streamline your search. >>> >>> -- Hannes >>> >> >> I read the first four and a half chapters from the Pro Git book pdf. >> So I think I understood that much. >> >> But in my situation, I do need a server so that other developers can >> access anytime over the internet. >> >> I should have mentioned that. > > I guess I'm confused.  The fourth chapter of the Pro Git book is > entirely about setting up your own Git server, including basically > step by step instructions on Gitolite and Gitosis, in addition to > simply running your own ssh-based server plus gitweb.  It is like 20 > pages long - how is this not exactly what you're asking for? > > Scott > Scott -- the man himself! I've been reading the pdf version of the excellent Pro Git book: http://progit.org/ebook/progit.pdf In the pdf version, Chapter 5 covers "Git on the Server". I was a little confused at section 5.2, "Getting Git on a Server". I was expecting a process very similar to installing on a work station (sections 2.4, "Installing Git", and 2.5, "First-Time Git Setup"), with differences pertaining to the server. But this section (5.2) didn't talk about that and seemed to assume I already installed Git on the server. Instead, this section explains how to create a bare repository and Section 5.2.1 explains how to put the bare repository on the server. So I jumped ahead to section 5.4, "Setting Up the Server", hoping to find the process I was expecting. For the most part it was there. But I was left pondering how tedious it would be to manage a couple dozen git users. So I read sections 5.7 "Gitosis" and 5.8 "Gitolite". It sounds like these two tools do the same thing. Since I'm not sure what makes them different, I wasn't sure which one would fit my needs. Then, I heard about Gitorious and would like to give that a spin. The idea of installing a single piece of software that does everything seems more appealing than installing and configuring multiple pieces of software. I'll return to the books for now and do the best I can. I'm running the Git server in a VirtualBox VM server and keep snapshots after significant changes. So if I break anything, it will be a couple clicks to recover. Thanks for everyone's help. ```