# Pointers to setup an internal git repository with access control

5 messages from 2011-08-30 to 2011-08-30. Participants: robert mena, Konstantin Khomoutov, Magnus Bäck.
Thread: https://gitlist.dev/t/28261

## robert mena, 2011-08-30 12:01

Subject: Pointers to setup an internal git repository with access control
Message-ID: <CAAZ43xZPsw2CnqOtb6wO7dRC1eMd0eweQ30w-wfzUHL5cqw=Yw@mail.gmail.com>
URL: https://gitlist.dev/e/CAAZ43xZPsw2CnqOtb6wO7dRC1eMd0eweQ30w-wfzUHL5cqw%3DYw%40mail.gmail.com

```
Hi,

I am trying to migrate from SVN to git and so I am looking for tools
that help me create an interal repository.  I currently use SVN over
HTTPS/Dav using the access.conf to be able to control which uses can
read/write to the repos or given branches.

Ideally I am looking for tools that enable me to do the same with git.

Regards.

```

## Konstantin Khomoutov, 2011-08-30 12:22

Subject: Re: Pointers to setup an internal git repository with access control
Message-ID: <20110830162223.1cbf9f98.kostix@domain007.com>
URL: https://gitlist.dev/e/20110830162223.1cbf9f98.kostix%40domain007.com
In-Reply-To: <CAAZ43xZPsw2CnqOtb6wO7dRC1eMd0eweQ30w-wfzUHL5cqw=Yw@mail.gmail.com>

```
On Tue, 30 Aug 2011 08:01:44 -0400
robert mena <robert.mena@gmail.com> wrote:

> I am trying to migrate from SVN to git and so I am looking for tools
> that help me create an interal repository.  I currently use SVN over
> HTTPS/Dav using the access.conf to be able to control which uses can
> read/write to the repos or given branches.
> 
> Ideally I am looking for tools that enable me to do the same with git.
Possibly look at smart http protocol [1], [2].

I may be wrong, but this access method cannot be used to implemet
access control with branch-level granularity.  If you really need this,
use gitolite [3].

1. http://progit.org/2010/03/04/smart-http.html
2. http://www.kernel.org/pub/software/scm/git/docs/git-http-backend.html
3. https://github.com/sitaramc/gitolite

```

## robert mena, 2011-08-30 12:35

Subject: Re: Pointers to setup an internal git repository with access control
Message-ID: <CAAZ43xYhFQzBVmjfnvRoboNPQ1OLtyq57=0ZL3B6p+dRWnJZ-g@mail.gmail.com>
URL: https://gitlist.dev/e/CAAZ43xYhFQzBVmjfnvRoboNPQ1OLtyq57%3D0ZL3B6p%2BdRWnJZ-g%40mail.gmail.com
In-Reply-To: <20110830162223.1cbf9f98.kostix@domain007.com>

```
Hi,

Thanks for the reply.  I'll take a look.

I don't have to use https+dav, it can be ssh as long as it is
encrypted and I have some sort of access control.  The branches item
is to be able to control who can merge/commit things back to, for
example, the trunk or whatever I call the "live" branch.

This way the devs can do what they want but the final merge to the
"live" branch would be done after the Q&A approves.

On Tue, Aug 30, 2011 at 8:22 AM, Konstantin Khomoutov
<flatworm@users.sourceforge.net> wrote:
> On Tue, 30 Aug 2011 08:01:44 -0400
> robert mena <robert.mena@gmail.com> wrote:
>
>> I am trying to migrate from SVN to git and so I am looking for tools
>> that help me create an interal repository.  I currently use SVN over
>> HTTPS/Dav using the access.conf to be able to control which uses can
>> read/write to the repos or given branches.
>>
>> Ideally I am looking for tools that enable me to do the same with git.
> Possibly look at smart http protocol [1], [2].
>
> I may be wrong, but this access method cannot be used to implemet
> access control with branch-level granularity.  If you really need this,
> use gitolite [3].
>
> 1. http://progit.org/2010/03/04/smart-http.html
> 2. http://www.kernel.org/pub/software/scm/git/docs/git-http-backend.html
> 3. https://github.com/sitaramc/gitolite
>

```

## Konstantin Khomoutov, 2011-08-30 12:59

Subject: Re: Pointers to setup an internal git repository with access control
Message-ID: <20110830165937.188baae9.kostix@domain007.com>
URL: https://gitlist.dev/e/20110830165937.188baae9.kostix%40domain007.com
In-Reply-To: <CAAZ43xYhFQzBVmjfnvRoboNPQ1OLtyq57=0ZL3B6p+dRWnJZ-g@mail.gmail.com>

```
On Tue, 30 Aug 2011 08:35:22 -0400
robert mena <robert.mena@gmail.com> wrote:

[...]
> I don't have to use https+dav, it can be ssh as long as it is
> encrypted and I have some sort of access control.  The branches item
> is to be able to control who can merge/commit things back to, for
> example, the trunk or whatever I call the "live" branch.
> 
> This way the devs can do what they want but the final merge to the
> "live" branch would be done after the Q&A approves.
Go for gitolite then.

```

## Magnus Bäck, 2011-08-30 18:33

Subject: Re: Pointers to setup an internal git repository with access control
Message-ID: <20110830183346.GA14605@jpl.local>
URL: https://gitlist.dev/e/20110830183346.GA14605%40jpl.local
In-Reply-To: <CAAZ43xZPsw2CnqOtb6wO7dRC1eMd0eweQ30w-wfzUHL5cqw=Yw@mail.gmail.com>

```
On Tuesday, August 30, 2011 at 14:01 CEST,
     robert mena <robert.mena@gmail.com> wrote:

> I am trying to migrate from SVN to git and so I am looking for tools
> that help me create an interal repository.  I currently use SVN over
> HTTPS/Dav using the access.conf to be able to control which uses can
> read/write to the repos or given branches.
> 
> Ideally I am looking for tools that enable me to do the same with git.

Gerrit Code Review (http://code.google.com/p/gerrit/) provides
branch-level ACLs for both reading and writing.

-- 
Magnus Bäck                   Opinions are my own and do not necessarily
SW Configuration Manager      represent the ones of my employer, etc.
Sony Ericsson

```
