Changelog:
2013-03-24 v3.5 (2 minor backward compat breakages)
1. 'DEFAULT_ROLE_PERMS' replaced by per repo
'default.roles' option
2. 'gitolite list-memberships' now requires a '-r' or a
'-u' flag
new 'gitolite owns' command (thanks to Kevin Pulo)
a) refer 'perl' in their Makefile, or
b) have a directory name of p5-*, or
c) have any dependency on any p5-* package
Like last time, where this caused no complaints.
Changelog:
2012-12-29 v3.3 bug fix: gl-perms propagation to slaves broke sometime
after v3.2 (so if you're only picking up tagged releases
you're OK)
the "D" command now allows rm/unlock to be totally
disabled
new trigger: update-gitweb-daemon-from-options; another
way to update gitweb and daemon access lists
new 'create' command for explicit wild repo creation, and
new AutoCreate trigger to control auto-creation
allow simple macros in conf file
2012-11-14 v3.2 major efficiency boost for large setups
optional support for multi-line pubkeys; see
src/triggers/post-compile/ssh-authkeys-split
bug fix for not creating gl-conf when repo para has only
config lines and no access rules
new 'bg' trigger command to put long jobs started from a
trigger into background
%GL_REPO and %GL_CREATOR now work for 'option's also
test suite now much more BSD friendly
2012-10-05 v3.1 (security) fix path traversal on wild repos
new %GL_CREATOR variable for git-config lines
rsync command to create and send bundles automagically
migrated 'who-pushed'
logical expressions on refexes!!!
Gitolite is an SSH-based gatekeeper providing access control for
a server that hosts many git repositories. Without gitolite, each
developer needing to push to one of the repositories hosted would
need a user account on that server; gitolite lets you do that just
using SSH public keys tied to a single, common, user that hosts
all the repositories.
Gitolite can restrict who can read (clone/fetch) from or write
(push) to a repository, and who can push to what branch or tag -
an important issue in corporate environments. Other features include:
* access control by branch-name or by modified file/directory;
* per-developer "personal namespace" prefixes;
* simple but powerful configuration file syntax (with validation);
* config files (and authority for maintaining them) can be split;
* easy integration with gitweb;
* comprehensive logging;
* easy migration from gitosis.
