master TOC | chapter TOC | support | license
WARNING: This is not the latest gitolite; please see the README
[NOTE: I would appreciate help testing these instructions]
Here's the simplest set of instructions, assuming the destination is a recent gitolite (has the 'gl-admin-push' command). Unless specified, all steps are on the new server.
install gitolite. Don't worry about the pubkey used in the gl-setup step -- for example this will do fine:
ssh-keygen -q -N '' -f dummy gl-setup -q dummy.pub
edit the rc file to have similar settings to the old one.
Do not copy the entire file outright -- some of the variables (notably
GL_PACKAGE_HOOKS) are installation dependent and
should not be touched! Do a diff or a vimdiff and copy across only what
you know you changed on the old server.
disable the old server so your users will not push any changes to it.
There are several ways to do this, but the simplest is to insert this line
at the top of
~/.gitolite.rc on the old server:
copy the contents of
$REPO_BASE in the old server to
the new server. By default, as you know, these are both
chown -R the files to the correct user if you copied using root.
fix up the hooks
trigger a push to the admin repo
git clone repositories/gitolite-admin.git /tmp/gitolite-admin cd /tmp/gitolite-admin git commit --allow-empty -m 'trigger compile on new server' gl-admin-push -f