Git development
 help / color / mirror / Atom feed
From: Mark Hills <Mark.Hills@framestore.com>
To: Sitaram Chamarty <sitaramc@gmail.com>
Cc: Konstantin Khomoutov <flatworm@users.sourceforge.net>,
	git@vger.kernel.org
Subject: Re: Clone to an SSH destination
Date: Mon, 3 Sep 2012 14:15:27 +0100 (BST)	[thread overview]
Message-ID: <alpine.LFD.2.01.1209031410450.5945@sys880.ldn.framestore.com> (raw)
In-Reply-To: <CAMK1S_iSbDNc39XjWZLgUJuBg71+A+CHbEq09QG+mntDQrdNxw@mail.gmail.com>

On Mon, 3 Sep 2012, Sitaram Chamarty wrote:

> 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

  reply	other threads:[~2012-09-03 13:15 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-03 10:21 Clone to an SSH destination Mark Hills
2012-09-03 11:26 ` Ævar Arnfjörð Bjarmason
2012-09-03 13:07   ` Mark Hills
2012-09-03 14:08     ` Konstantin Khomoutov
2012-09-03 14:26       ` Sitaram Chamarty
2012-09-03 14:27     ` Enrico Weigelt
2012-09-03 11:47 ` Konstantin Khomoutov
2012-09-03 12:54   ` Sitaram Chamarty
2012-09-03 13:15     ` Mark Hills [this message]
2012-09-03 13:48       ` Sitaram Chamarty

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=alpine.LFD.2.01.1209031410450.5945@sys880.ldn.framestore.com \
    --to=mark.hills@framestore.com \
    --cc=flatworm@users.sourceforge.net \
    --cc=git@vger.kernel.org \
    --cc=sitaramc@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox