If you are having enough background, this article is a shortcut for you to set up a group of SVN servers with one master and one slave (you should be able to generalize it to multiple slaves with some minor touches). This group of SVN servers could be synchronized (or replicated) to allow multi-site deployment for network efficiency. However, you could always refer to this article for details on setting up svnsync and this article for setting up ssh login without password.
Assumed you are given:
- A master SVN server ([Master]) access via HTTP with a proper repository setup at /var/svn/repos. (You could refer to this article for setting up an SVN server.)
- A slave SVN server ([Slave]) accessed via HTTP (with an empty repository /var/svn/repos created as in this article).
- The credentials for accessing the master and slave SVN servers are identical.
- The master and slave SVN servers can access each other.
To set this up, follow the recipe:
- [Slave] cd /etc/apache2/mods-enabled; sudo ln -s ../mods-available/proxy.load; sudo ln -s ../mods-available/proxy_http.load
- [Slave] Add a SVNMasterURI directive under the <Location> directive in /etc/apache2/mods-available/dav_svn.conf (details)
- [Slave] sudo adduser svnsync
- [Slave] sudo adduser svnsync svn
- [Slave] sudo chown -R svnsync:svn /var/svn/repos
- [Slave] Create a script /var/svn/repos/hooks/pre-revprop-change (details)
- [Slave] sudo chmod +x /var/svn/repos/hooks/pre-revprop-change
- [Slave] sudo svnsync init –username svnsync file:///var/svn/repos http://<master hostname>/svn/repos
- [Slave] Download the script svn-sync-slave.sh and put under /var
- [Slave] Modify the first line of /var/svn-sync-slave.sh from #!/bin/sh to #!/bin/bash
- [Slave] sudo chown svnsync:svn /var/svn-sync-slave.sh; sudo chmod +x /var/svn-sync-slave.sh
- [Master] Create a script /var/svn/repos/hooks/post-commit (details)
- [Master] sudo chown www-data:svn /var/svn/repos/hooks/post-commit; sudo chmod g+rws /var/svn/repos/hooks/post-commit
- [Master] sudo -i
- [Master] su – www-data
- [Master] ssh-keygen -t rsa (give empty passphrase)
- [Master] ssh svnsync@<slave hostname> mkdir -p .ssh
- [Master] cat .ssh/id_rsa.pub | ssh svnsync@<slave hostname> ‘cat >> .ssh/authorized_keys’
To test this setup:
- Find another computer with svn client installed. ([Client])
- [Client] svn import –username <user> <path to local folder> http://<slave hostname>/svn/repos
- Check whether the imported folders and files are in both master and slave SVN servers’ repositories.
- [Client] Pick any one file imported. Modify it and commit it to http://<slave hostname>/svn/repos.
- Check whether the modified file is in both master and slave SVN servers’ repositories.
Update on 2011-07-28:
There is something subtle that needs special consideration.
In fact, when I try to apply this procedures to an old and big svn repository, there is a problem. I tried to start synchronizing with a new repository (you have to start from scratch anyway!) over the network. I then tried to do a rough gauging and calculation exercise. It needs to take 3 months to sync them all (yes, days and nights, continuously).
Luckily, we resolved it by using the file-based nature of svn. We first make a sync in the same machine. But note that you should use the target url as the master url, i.e. you should use IP / hostname to sync instead of localhost as svnsync remembers the url you used to init the sync process.
Then, after the sync process is done (which is much much much faster), zip the whole repository and upload to the target slave machine. In the slave machine, you could expand and rename the repository as you like. At this point, the svnsync becomes incremental. So it would not take you much time to do a few revisions’ synchronization.
SVNMasterURI http://<master hostname>/svn/repos
#!/bin/sh USER="$3" if [ "$USER" != "svnsync" ]; then echo >&2 "Only the svnsync user can change revprops" exit 1 fi exit 0
#!/bin/sh ssh -l svnsync <slave hostname> "/var/svn-sync-slave.sh -r /var/svn/repos"