master TOC | chapter TOC | support

the conf/gitolite.conf file

One goal I have is to minimise the code changes to "core" gitolite due to this, so all repo-specific mirror settings are stored as git config variables (you know you can specify git config variables in the gitolite config file right?). These are:

• gitolite.mirror.master

  The name of the server which is the master for this repo. Each server will compare this with $GL_HOSTNAME (from its own rc file) to determine if it's the master or a slave. Here're the possible values:

  • undefined or local: this repo is local to this server
  • same as $GL_HOSTNAME: this server is the "master" for this repo. (The repo is "native" to this server).
  • not same as $GL_HOSTNAME: this server is a "slave" for the repo. (The repo is a non-native on this server).

• gitolite.mirror.slaves

  Ignored for non-native repos. For native repos, this is a space-separated list of servers to push to from the post-receive hook.

  Clearly, you can have different sets of slaves for different repos (again, see "discussion" section later for more on this).

• gitolite.mirror.redirectOK

  See the section on "redirecting pushes"

• In addition, you can create your own slave lists, named whatever you want, except they have to start with gitolite.mirror.. The section on "commands to (re-)sync mirrors" has some examples.