0

I want to setup a Gitolite based installation for hosting git repositories in a small organization for a limited set of projects (100 projects at most, probably less than 30) with repositories under directories like

gitolite@hostname:some_project/
gitolite@hostname:project_teletubby/

I will use an LDAP-backed SSH server public-key based authentication so I don't need Gitolite to manage authentication keys.

Instead of using a single configuration repository (gitolite@hostname:gitolite-admin.git) how can I allow project managers to use their own configuration repositories (e.g. gitolite@hostname:projectName/gitolite-admin.git) to manage everything beneath their projectName/ path without read and write access to configurations of other projects?

jotik
  • 159
  • 6
  • http://gitolite.com/gitolite/gitolite.html#deleg – Sven Nov 11 '14 at 08:46
  • Unfortunately, using the Gitolite `subconf` command is not an option, because project managers will still have read access to the whole `gitolite@hostname:gitolite-admin.git` repository and can read the configurations of other projects as well. – jotik Nov 11 '14 at 09:08
  • Then Gitolite is the wrong tool for you. – Sven Nov 11 '14 at 09:11
  • @SvW I still think it may be possible by writing some wrapper between `.ssh/authorized_keys` and Gitolite which rewrites the repository name in `SSH_ORIGINAL_COMMAND` and then somehow calls `gitolite-shell`. – jotik Nov 11 '14 at 09:19
  • 1
    Might be, but it's likely not supported. Why don't use a tool that fits your requirements from the start instead of trying to coax another to do something it's not supposed to do? – Sven Nov 11 '14 at 09:22

0 Answers0