master TOC | chapter TOC | support

autonomous

In many ways this is the simplest setup.

The slave server belongs to someone else. Their admin has final say on what goes into their gitolite-admin repo and thus their server's config. The gitolite-admin repo is NOT mirrored, and mirroring of individual repos (i.e., actual config lines included) is by negotiation/agreement between the admins.

Authentication info is not common. The master has no real control over who can read the repos on the slave. Allowing redirected pushes is not a good idea, unless you have other means of trust (administrative, contractual, legal, etc.)

Best for open source projects with heavy "fetch" load compared to "push".