master TOC
|
chapter TOC
|
support
some more features
Here're some more features.
- simple, yet powerful, config file syntax, including specifying
gitweb/daemon access. You'll need this power if you manage lots of
users+repos+combinations of access
- apart from branch-name based restrictions, you can also restrict by
file/dir name changed (i.e., output of
git diff --name-only)
- if your requirements are still too complex, you can split up the config
file and delegate authority over parts of it
- easy to specify gitweb owner, description and gitweb/daemon access
- easy to sync gitweb (http) authorisation with gitolite's access config
- comprehensive logging [aka: management does not think "blame" is just a
synonym for "annotate" :-)]
- "personal namespace" prefix for each dev
- migration guide and simple converter for gitosis conf file
- "exclude" (or "deny") rights at the branch/tag level
- specify repos using patterns (patterns may include creator's name)
- define powerful operations on the server side, even github-like forking