From: Sitaram Chamarty <sitaramc@gmail.com>
To: ken edward <kedward777@gmail.com>
Cc: Fredrik Gustafsson <iveqy@iveqy.com>, git@vger.kernel.org
Subject: Re: git repo vs project level authorization
Date: Wed, 7 Dec 2016 21:18:43 +0530 [thread overview]
Message-ID: <20161207154843.GB24934@sita-lt.atc.tcs.com> (raw)
In-Reply-To: <20161205220444.GB12249@paksenarrion.iveqy.com>
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
prev parent reply other threads:[~2016-12-07 16:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
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 message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20161207154843.GB24934@sita-lt.atc.tcs.com \
--to=sitaramc@gmail.com \
--cc=git@vger.kernel.org \
--cc=iveqy@iveqy.com \
--cc=kedward777@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).