git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: Anybody home?

From
Joshua Stoutenburg <jehoshua02@gmail.com>
Date
Sep 15, 2011, 21:00 UTC
Message-ID
<CAOZxsTq0qMB_Y97WcodVbO6DmXRXBpP_at3SF-VkPbbcnDfjgw@mail.gmail.com>
In-Reply-To
<CAP2yMaJcKnghtxxDNVYk=00KQ-ZOGEwACHRTU15tGnOuk3R4Hw@mail.gmail.com>
On Thu, Sep 15, 2011 at 8:04 AM, Scott Chacon <schacon@gmail.com> wrote:
Show 32 quoted lines
> Hey,
>
> On Thu, Sep 15, 2011 at 2:01 AM, Joshua Stoutenburg
> <jehoshua02@gmail.com> 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.
Previous: Scott ChaconNext: Joshua Stoutenburg
Message 19 of 20 in “Anybody home?”
  1. Joshua StoutenburgSep 15, 2011
  2. Michael WittenSep 15, 2011
  3. Joshua StoutenburgSep 15, 2011
  4. Joshua StoutenburgSep 15, 2011
  5. Alexander KostikovSep 15, 2011
  6. Ted Ts'oSep 15, 2011
  7. Jakub NarebskiSep 15, 2011
  8. Johannes SixtSep 15, 2011
  9. Thomas RastSep 15, 2011
  10. Joshua StoutenburgSep 15, 2011
  11. Martin LanghoffSep 15, 2011
  12. Joshua StoutenburgSep 15, 2011
  13. Carlos Martín NietoSep 15, 2011
  14. Joshua StoutenburgSep 15, 2011
  15. Miles BaderSep 15, 2011
  16. Carlos Martín NietoSep 15, 2011
  17. Joshua StoutenburgSep 15, 2011
  18. Scott ChaconSep 15, 2011
  19. Joshua StoutenburgSep 15, 2011
  20. Joshua StoutenburgSep 15, 2011

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.