Re: git repo vs project level authorization

From: Sitaram Chamarty <sitaramc@gmail.com>
Date: Dec 7, 2016, 15:48 UTC
Message-ID: <20161207154843.GB24934@sita-lt.atc.tcs.com>
In-Reply-To: <20161205220444.GB12249@paksenarrion.iveqy.com>

Ken,

On Mon, Dec 05, 2016 at 11:04:44PM +0100, Fredrik Gustafsson wrote:

Show 16 quoted lines

> On Mon, Dec 05, 2016 at 03:33:51PM -0500, ken edward wrote:
> > I am currently using svn with apache+mod_dav_svn to have a single
> > repository with multiple projects. Each of the projects is controlled
> > by an access control file that lists the project path and the allowed
> > usernames.
> > 
> > Does git have this also? where is the doc?
> > 
> > Ken
> 
> Git does not do hosting or access control. For this you need to use a
> third party program. There are plenty of options for you and each has
> different features and limitations. For example you should take a look
> at gitolite, gitlab, bitbucket, github, gogs. Just to mention a few.
> It's also possible to setup git with ssh or http/https with your own
> access control methods. See the progit book for details here.

For some reason I did not see your email so I am responding to Fredrik's.

If your current system is an access control file, gitolite may be the closest "in spirit" to what you have;

The others that Fredrik mentioned are all much more GUI (and all of them have additional features like issue tracking, code reiew, etc.) If you need a more github-like experience, try those out.

Gitolite does *only* access control, nothing else, but within that limited scope it's pretty powerful. The simplest/quickest overview is probably this:

    http://gitolite.com/gitolite/overview.html#basic-use-case

regards sitaram