Re: "trying out" gitolite with minimum impact on a system

From: Sitaram Chamarty <sitaramc@gmail.com>
Date: Oct 12, 2011, 07:52 UTC
Message-ID: <CAMK1S_juQRRNhCMDx4Wdp+QwAZBQBvBYYQ06AdS_P2fdtLqBtg@mail.gmail.com>
In-Reply-To: <CAGK7Mr6cnP6QQwGswWwQYiGR2_BUjMPz+VsygQXb0Voehm+akg@mail.gmail.com>

On Wed, Oct 12, 2011 at 11:45 AM, Philippe Vaucher <philippe.vaucher@gmail.com> wrote:

Show 13 quoted lines

>> After that, entirely within that user, you have an admin user and six
>> normal users, to do with as you please.  You emulate different users
>> simply by using a different username in the URL, like "git clone
>> u1:reponame" versus "git clone u2:reponame".
>
> Hum, except if I missed something the classic way to use gitolite is
> to always clone using the same user (git@host:repository.git), and the
> "real" identification is done by the ssh keys (which means that
> contrary to plain ssh you lose the ability to have two users with the
> same ssh key, which should never happen anyway).
>
> But maybe you're refering to an alternate authentification mechanism
> within gitolite I'm unaware of.

you should read "entirely within that user" as "entirely within that new, possibly throw-away, Unix userid you created". This is meant to fit with the subject line's "minimum impact on a system" phrase.

regards

sitaram