Re: Clone to an SSH destination

From: Mark Hills <mark.hills@framestore.com>
Date: Sep 3, 2012, 13:15 UTC
Message-ID: <alpine.LFD.2.01.1209031410450.5945@sys880.ldn.framestore.com>
In-Reply-To: <CAMK1S_iSbDNc39XjWZLgUJuBg71+A+CHbEq09QG+mntDQrdNxw@mail.gmail.com>

On Mon, 3 Sep 2012, Sitaram Chamarty wrote:

Show 26 quoted lines

> On Mon, Sep 3, 2012 at 5:17 PM, Konstantin Khomoutov
> <flatworm@users.sourceforge.net> wrote:
> > On Mon, 3 Sep 2012 11:21:43 +0100 (BST)
> > Mark Hills <Mark.Hills@framestore.com> wrote:
> 
> [snip]
> 
> >> This is quite cumbersome; we have a large team of devs who use a
> >> simple 'git clone' to an NFS directory, but we wish to retire NFS
> >> access.
> 
> [snip]
> 
> > gitolite kind of implements this ("wild repos") [1], you could look if
> > it suits your needs.
> 
> The simplest conf to do what you want in gitolite is something like this:
> 
>     repo [a-zA-Z0-9]..*
>         C   =   @all
>         RW+ =   @all
> 
> But of course your *user* authentication will probably change quite a
> bit, since gitolite runs as one Unix user and merely simulates many
> "gitolite users", while in the NFS method each of your devs probably
> has a full login to the server.

I'll check out gitolite, thanks.

We use unix users extensively (groups, permissions etc.) with YP, and this works well; a separate permissions scheme is not very desireable.

The ssh method works very well right now, and nicely transparent. It's only the initial clone/creation that is harder than it was over NFS. And it prevents the use of git-shell too.

Thanks

-- 
Mark