git repo vs project level authorization

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

On Mon, Dec 05, 2016 at 03:33:51PM -0500, ken edward wrote:

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.

Ken,

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

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

ken edward <kedward777@gmail.com> writes:

It is customary not to mix unrelated projects into a single repository in the Git land. Some hosting solutions give access control per branches, and some others give access control per repositories.