git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: Pointers to setup an internal git repository with access control

From
RMrobert mena <robert.mena@gmail.com>
Date
Aug 30, 2011, 12:35 UTC
Message-ID
<CAAZ43xYhFQzBVmjfnvRoboNPQ1OLtyq57=0ZL3B6p+dRWnJZ-g@mail.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:

Show 19 quoted lines
> 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
>
Previous: Konstantin KhomoutovNext: Konstantin Khomoutov
Message 3 of 5 in “Pointers to setup an internal git repository with access control”
  1. robert menaAug 30, 2011
  2. Konstantin KhomoutovAug 30, 2011
  3. robert menaAug 30, 2011
  4. Konstantin KhomoutovAug 30, 2011
  5. Magnus BäckAug 30, 2011

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.