* git repo vs project level authorization @ 2016-12-05 20:33 ken edward 2016-12-05 21:59 ` Junio C Hamano 2016-12-05 22:04 ` Fredrik Gustafsson 0 siblings, 2 replies; 4+ messages in thread From: ken edward @ 2016-12-05 20:33 UTC (permalink / raw) To: git 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 ^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: git repo vs project level authorization 2016-12-05 20:33 git repo vs project level authorization ken edward @ 2016-12-05 21:59 ` Junio C Hamano 2016-12-05 22:04 ` Fredrik Gustafsson 1 sibling, 0 replies; 4+ messages in thread From: Junio C Hamano @ 2016-12-05 21:59 UTC (permalink / raw) To: ken edward; +Cc: git ken edward <kedward777@gmail.com> writes: > 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? 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. ^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: git repo vs project level authorization 2016-12-05 20:33 git repo vs project level authorization ken edward 2016-12-05 21:59 ` Junio C Hamano @ 2016-12-05 22:04 ` Fredrik Gustafsson 2016-12-07 15:48 ` Sitaram Chamarty 1 sibling, 1 reply; 4+ messages in thread From: Fredrik Gustafsson @ 2016-12-05 22:04 UTC (permalink / raw) To: ken edward; +Cc: git 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. -- Fredrik Gustafsson phone: +46 733-608274 e-mail: iveqy@iveqy.com website: http://www.iveqy.com ^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: git repo vs project level authorization 2016-12-05 22:04 ` Fredrik Gustafsson @ 2016-12-07 15:48 ` Sitaram Chamarty 0 siblings, 0 replies; 4+ messages in thread From: Sitaram Chamarty @ 2016-12-07 15:48 UTC (permalink / raw) To: ken edward; +Cc: Fredrik Gustafsson, git Ken, On Mon, Dec 05, 2016 at 11:04:44PM +0100, Fredrik Gustafsson wrote: > 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 ^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2016-12-07 16:02 UTC | newest] Thread overview: 4+ messages (download: mbox.gz follow: Atom feed -- links below jump to the message on this page -- 2016-12-05 20:33 git repo vs project level authorization ken edward 2016-12-05 21:59 ` Junio C Hamano 2016-12-05 22:04 ` Fredrik Gustafsson 2016-12-07 15:48 ` Sitaram Chamarty
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for NNTP newsgroup(s).