git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: building git ; need suggestion

From
JBJoydeep Bakshi <joydeep.bakshi@infoservices.in>
Date
Mar 15, 2013, 12:52 UTC
Message-ID
<00107242-04EB-423F-90FE-A6DCDEE7E262@infoservices.in>
In-Reply-To
<20130315124415.GA23122@paksenarrion.iveqy.com>
On 15-Mar-2013, at 6:14 PM, Fredrik Gustafsson <iveqy@iveqy.com> wrote:
Show 22 quoted lines
> 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?
Actually the branches have to be dedicated to a group of users.
 developer branch ---> developers
bug fixed branch --- > bug fixer

and specific group don't need to RW permission on other branch. Obviously the admin must have the full permission on all these branches and merge as per requirement.

The web-interface is required for checking the history by the users themselves
and for code review. I don't know any web interface which can show repo/branch 
based on authentication. I have tried gitweb but it can handle a single repo or multiple
repo with single authentication. NO ACL
Previous: Fredrik GustafssonNext: Magnus Bäck
Message 4 of 10 in “building git ; need suggestion”
  1. Joydeep BakshiMar 15, 2013
  2. Joydeep BakshiMar 15, 2013
  3. Fredrik GustafssonMar 15, 2013
  4. Joydeep BakshiMar 15, 2013
  5. Magnus BäckMar 15, 2013
  6. Joydeep BakshiMar 18, 2013
  7. Joydeep BakshiMar 18, 2013
  8. David AguilarMar 19, 2013
  9. Paul CampbellMar 15, 2013
  10. Konstantin KhomoutovMar 15, 2013

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.