On Thu, 13 Sep 2012 04:38:39 -0700 (PDT)
maxhodges <m...@whiterabbitpress.com> wrote:

> I finally got it installed after spending hours of web research. This
> is the command I had to use:
> $ rpm -Uvh http://repo.webtatic.com/yum/centos/5/latest.rpm
> $ yum install --disableexcludes=main --enablerepo=webtatic git-all 

Well, the first hit I got googling for git+centos+5 is
which tells there's a repo containing ready-made Git packages.
I do not use CentOS so can't verify this but that guide I linked to
does not appear to be complex to me.

> But then I get stuck on the next set of instructions:
> http://git-scm.com/book/en/Git-on-the-Server-Setting-Up-the-Server
> first, $ sudo adduser git
> results in:  sudo: useradd: command not found
> someone on stackoverflow suggested I run this instead:
> $sudo /usr/sbin/useradd git
> that seemed to work, too bad it wasn't in the documentation.
What documentation?  You referred to a book; a book is a text *broadly*
covering its subject, it's not an "Installing Git on CentOS 5" HOWTO

In either case, adding (system) users on a Unix system is a basic
sysadmin skill, something a sysadmin learns to do in the first few
hours of their training.  I dunno why you are blindly following
the letter of someone's blog post or a random book on the subject
instead of getting the essense of them and applying it in a way which
is best for your particular system.

> Next it says, "Next, you need to add some developer SSH public keys
> to the authorized_keys file for that user. Let’s assume you’ve
> received a few keys by e-mail and saved them to temporary files.:
> Unfortunately I haven't received any by email. (??) I'm trying to set
> this up but this is a deadend for me.
The text you cited clearly reads "Let's assume ...", and it merely
means that the text's author decided to not delve into the topic of
generation of SSH keys and instead they assumed the
prospective developers generate their SSH keys for themselves on their
own machines and send you (the Git administrator) the public parts of
those keys.  Your particular organisation might have other policy for
this, for instance, *you* generate keys for the developers and then
hand them out to those developers while keeping the public parts of
these keys to yourself.  Or you might decide to not use SSH for
accessing your Git repositories and instead serve them over HTTP[S]
using whatever HTTP authentication scheme you decide (including, say,
Negotiate which supports Kerberos/SSPI and enables SSO in Windows

> Over the years I've installed
> many complex web apps including Magento eCommerce, X-Cart, Kayako
> helpdesk, Xenforo and other forum systems, WordPress, and many other
> apps. Why can't installing Git be as easy as any of those? Keep in
> mind, Git can be used for documents and design files, not just for
> the source code of UNIX developers. Unlike many other web apps, it
> seems you have to be a very experienced UNIX sysadmin in order to get
> this software installed. 

Sorry but it looks like you're trying to install Git having no clean
goals of what you really want to achieve.  This is not gonna work this
way because it never works this way.  Git is not a webapp which has
precisely one use (to be a webapp), it's a flexible tool which, when
being deployed on a server, requires up-front thinking about what kind
of setup you intend to get as the result: which protocols to use for
accessing the repositories, how to manage users and their access
permissions.  And if you for example decide to use SSH for accessing
Git repos, it's obviously supposed you have to possess basic to
intermediate level of knowledge of SSH, including what are SSH keys and
how pubkey-based authentication works in SSH.

You received this message because you are subscribed to the Google Groups "Git 
for human beings" group.
To post to this group, send email to git-users@googlegroups.com.
To unsubscribe from this group, send email to 
For more options, visit this group at 

Reply via email to