{"thread":{"id":"44626","subject":"git repo vs project level authorization","startedAt":"2016-12-05T20:34:07Z","lastAt":"2016-12-07T16:02:32Z","messageCount":4,"participants":["ken edward","Fredrik Gustafsson","Junio C Hamano","Sitaram Chamarty"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"306958","messageId":"CAAqgmoO+7cLZHpX61=Mh7PjqrCUc0qyFD=C+sjVat_+KPhisbw@mail.gmail.com","threadId":"44626","inReplyTo":null,"subject":"git repo vs project level authorization","fromName":"ken edward","fromEmail":"kedward777@gmail.com","sentAt":"2016-12-05T20:33:51Z","receivedAt":"2016-12-05T20:34:07Z","isPatch":false,"sender":{"key":"kedward777@gmail.com","avatar":null},"body":"I am currently using svn with apache+mod_dav_svn to have a single\nrepository with multiple projects. Each of the projects is controlled\nby an access control file that lists the project path and the allowed\nusernames.\n\nDoes git have this also? where is the doc?\n\nKen\n"},{"id":"306968","messageId":"20161205220444.GB12249@paksenarrion.iveqy.com","threadId":"44626","inReplyTo":"CAAqgmoO+7cLZHpX61=Mh7PjqrCUc0qyFD=C+sjVat_+KPhisbw@mail.gmail.com","subject":"Re: git repo vs project level authorization","fromName":"Fredrik Gustafsson","fromEmail":"iveqy@iveqy.com","sentAt":"2016-12-05T22:04:44Z","receivedAt":"2016-12-05T21:59:10Z","isPatch":false,"sender":{"key":"iveqy@iveqy.com","avatar":"https://avatars.githubusercontent.com/u/761743?v=4"},"body":"On Mon, Dec 05, 2016 at 03:33:51PM -0500, ken edward wrote:\n> I am currently using svn with apache+mod_dav_svn to have a single\n> repository with multiple projects. Each of the projects is controlled\n> by an access control file that lists the project path and the allowed\n> usernames.\n> \n> Does git have this also? where is the doc?\n> \n> Ken\n\nGit does not do hosting or access control. For this you need to use a\nthird party program. There are plenty of options for you and each has\ndifferent features and limitations. For example you should take a look\nat gitolite, gitlab, bitbucket, github, gogs. Just to mention a few.\nIt's also possible to setup git with ssh or http/https with your own\naccess control methods. See the progit book for details here.\n\n-- \nFredrik Gustafsson\n\nphone: +46 733-608274\ne-mail: iveqy@iveqy.com\nwebsite: http://www.iveqy.com\n"},{"id":"306969","messageId":"xmqqvauy2g19.fsf@gitster.mtv.corp.google.com","threadId":"44626","inReplyTo":"CAAqgmoO+7cLZHpX61=Mh7PjqrCUc0qyFD=C+sjVat_+KPhisbw@mail.gmail.com","subject":"Re: git repo vs project level authorization","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2016-12-05T21:59:46Z","receivedAt":"2016-12-05T21:59:52Z","isPatch":false,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"ken edward <kedward777@gmail.com> writes:\n\n> I am currently using svn with apache+mod_dav_svn to have a single\n> repository with multiple projects. Each of the projects is controlled\n> by an access control file that lists the project path and the allowed\n> usernames.\n>\n> Does git have this also? where is the doc?\n\nIt is customary not to mix unrelated projects into a single\nrepository in the Git land.  Some hosting solutions give access\ncontrol per branches, and some others give access control per\nrepositories.\n"},{"id":"307138","messageId":"20161207154843.GB24934@sita-lt.atc.tcs.com","threadId":"44626","inReplyTo":"20161205220444.GB12249@paksenarrion.iveqy.com","subject":"Re: git repo vs project level authorization","fromName":"Sitaram Chamarty","fromEmail":"sitaramc@gmail.com","sentAt":"2016-12-07T15:48:43Z","receivedAt":"2016-12-07T16:02:32Z","isPatch":false,"sender":{"key":"sitaramc@gmail.com","avatar":"https://avatars.githubusercontent.com/u/43316?v=4"},"body":"Ken,\n\nOn Mon, Dec 05, 2016 at 11:04:44PM +0100, Fredrik Gustafsson wrote:\n> On Mon, Dec 05, 2016 at 03:33:51PM -0500, ken edward wrote:\n> > I am currently using svn with apache+mod_dav_svn to have a single\n> > repository with multiple projects. Each of the projects is controlled\n> > by an access control file that lists the project path and the allowed\n> > usernames.\n> > \n> > Does git have this also? where is the doc?\n> > \n> > Ken\n> \n> Git does not do hosting or access control. For this you need to use a\n> third party program. There are plenty of options for you and each has\n> different features and limitations. For example you should take a look\n> at gitolite, gitlab, bitbucket, github, gogs. Just to mention a few.\n> It's also possible to setup git with ssh or http/https with your own\n> access control methods. See the progit book for details here.\n\nFor some reason I did not see your email so I am responding to\nFredrik's.\n\nIf your current system is an access control file, gitolite may\nbe the closest \"in spirit\" to what you have;\n\nThe others that Fredrik mentioned are all much more GUI (and all\nof them have additional features like issue tracking, code\nreiew, etc.) If you need a more github-like experience, try\nthose out.\n\nGitolite does *only* access control, nothing else, but within\nthat limited scope it's pretty powerful.  The simplest/quickest\noverview is probably this:\n\n    http://gitolite.com/gitolite/overview.html#basic-use-case\n\nregards\nsitaram\n"}]}