gitbrowser is just another attempt to get rid of gitweb. While there are many Git web interfaces, only a few understand gitolite access control lists (gitbrowser only implements the absolute minimum).
All configuration is done through a
GITBROWSER dict in Django's
The following keys are recognized:
False, unauthenticated requests are redirected to the login page
%(paths)sfor formatting, or
repo, usernameas it's argument. The callable should produce a list of strings
gituser. Defaults to
GitoliteACL. If you only have public accessible repositories, use
GitoliteProjectsFileRepositoryLister, which uses the
display sub-dict takes the following keys:
If you use an acl implementation different from
AllowAllACL, make sure your Django user names and group names match those in gitolite. Since it is possible to evaluate group membership on the fly in gitolite, gitbrowser does not use the group memberships defined in gitolite's big conf or split conf. You have to duplicate the group membership in Django
ATTENTION: DO NOT USE gitbrowser's GitoliteACL implementation if you have permissions other the R(W)+ on .*
gitbrowser does not check for negative permissions (e.g. denied read access) nor does it check for permissions on refs.