Subversion Configuration

Create subversion repositories:

All our subversion repositories should be located in /var/svn in order to be visible to Apache (you can change /var/svn to any directory).

SSL (Secure Sockets Layer)

The following steps are required if you need SSL, otherwise skip this chapter.

“Listen 443″ should already exist in /etc/apache2/ports.conf, otherwise add it manually:

Create a new SSL config file (replace ssl.new.site with your preferred name):

Edit the file:

Replace:

with

Before </VirtualHost>, add:

You can try using the template from “default-ssl” instead of “default”, which is easier and more reliable since many SSL-related configurations are already handled. However, I haven’t tried this method and I’m not sure if it works without modifications.

Create SSL certificate file:

Enable the new site:

To see if the setup works, use your web browser to visit:

Replace server.ip with the ip of your server.
There should be a pop-up or an alert about the new certificate.

DAV_SVN Configuration

Edit /etc/apache2/mods-available/dav_svn.conf and follow the guidline:

Normally it looks like this:

Enable the mod and restart:

Create a user account for dav_svn:

To add more users, use:

Subversion Testing

It should says “Checked out revision 0.”, otherwise try looking for the errors on the Internet.
You probably forgot some steps or I forgot to mention some details.

Migration

Skip this chapter if you don’t need to migrate you data from your old server.

On the old server, we need to dump all updates into a single file. Each repository must be done separately.

Those dump files must be applied on the new system’s repositories.

Congratulations, all your source code has been migrated!