From: Fredrik Gustafsson <iveqy@iveqy.com>
To: Joydeep Bakshi <joydeep.bakshi@infoservices.in>
Cc: git@vger.kernel.org
Subject: Re: building git ; need suggestion
Date: Fri, 15 Mar 2013 13:44:15 +0100 [thread overview]
Message-ID: <20130315124415.GA23122@paksenarrion.iveqy.com> (raw)
In-Reply-To: <868B103B-690E-477B-BF75-8F954F893E6F@infoservices.in>
On Fri, Mar 15, 2013 at 05:54:05PM +0530, Joydeep Bakshi wrote:
> [1] the server will have different git repo with branches
> [2] there will be a web-based GUI which must be flexible to show just a specific branch of a repo based on user authentication
> [3] the web-based GUI should also have the flexibility to show a single repo based on the authentication
> [4] the web-based GUI should have an admin account to supervise and configure all repos along with their branches
> [3] there must be a control mechanism in the repo/web based GUI which have ACL on branches i.e.
> some specific users should see some specific/ or just a branch and able to commit there only.
>
> based on the above scenario could anyone suggest the best available solution ?
> There are many like gitolike/github etc…. but don't know whig one has much finer granular
> control/ACL/web-based GUI…
gitolite have a more fine ACL. Check it out. However it doesn't really
meet your needs with web-interface (and I'm not even sure about the ACL
thing is fine enough for you). You can read more about ACL in the git
book: http://git-scm.com/book/ch7-4.html
The webgui that's most populair is cgit and git-web. They don't do ACL
afaik.
Why would you need ACL? Why not don't share the branches that are going
to be secret? Or are you looking for some branches to be read only?
When we did this, we did a simple gitolite implementation ourself and
integrated cgit on our website wich already had ACL. It works well.
Howerver we do ACL on repo-level, not on branch level.
You can also look into git-submodules which will make it possible for
you to do repo-wide ACL.
However I'm not sure you will be using git in the way git is designed
too and even if it will work, maybe an other solution is better for you.
--
Med vänliga hälsningar
Fredrik Gustafsson
tel: 0733-608274
e-post: iveqy@iveqy.com
next prev parent reply other threads:[~2013-03-15 12:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-15 12:24 building git ; need suggestion Joydeep Bakshi
2013-03-15 12:43 ` Joydeep Bakshi
2013-03-15 12:44 ` Fredrik Gustafsson [this message]
2013-03-15 12:52 ` Joydeep Bakshi
2013-03-15 13:14 ` Magnus Bäck
2013-03-18 5:44 ` Joydeep Bakshi
2013-03-18 12:24 ` Joydeep Bakshi
2013-03-19 2:11 ` David Aguilar
2013-03-15 17:25 ` Paul Campbell
2013-03-15 13:56 ` Konstantin Khomoutov
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20130315124415.GA23122@paksenarrion.iveqy.com \
--to=iveqy@iveqy.com \
--cc=git@vger.kernel.org \
--cc=joydeep.bakshi@infoservices.in \
/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.
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).