As a long time SVN user it is the version control system I know the best (though I am not a fan of any version control implementations I’ve used so far, SVN is just the one I’ve used the most). I’ve never setup my own repository before and looked into doing so today for various code of my own that I develop locally. All in all it is a simple process, but there are a few gotchya’s that you have to look out for.
Guide I’m installing a svn repo on my local Fedora 8 laptop. Theoretically these instructions can be applied to any distro but you will probably have to modify some of the commands and file locations.
yum install subversion apache moddavsvn # install subversion, the apache server which will host it (there is a very basic ‘svnserver’ that comes with subversion, but this way is more widespread), and the apache module for svn
While we will be creating one repository and multiple projects under it, you can create as many repositories as you like and as many projects under each but you will need to tweak the apache configuration below (I will note the changes when we get there). Run the following command, replacing /tmp with the directory you wish to store the repository (this is to be applied from here on out in these instructions)
sudo svnadmin create /tmp/repos/
NOTE: The single repository in this case is named ‘repos’. This is because when clients access a project they will access it by checking out from http://serveruri/repos/projectname. Once again it is possible to create and access multiple repositories (one for each project if you wish) and that will involve some tweaking of the apache config below.
chown -R apache.apache /tmp/repos/
foobar/ foobar/branches/ foobar/tags/ foobar/trunk/ foobar/trunk/foobar/ foobar/trunk/foobar/docs foobar/trunk/foobar/src foobar/trunk/foobar/test foobar/trunk/foobar/Makefile .....
To import this project into the svn repository simply run the following command in the directory containing the top level
svn import foobar file:///tmp/repos/foobar -m 'Initial import' # don't forget to replace /tmp again
<Location /repos> DAV svn SVNPath /tmp/repos # Feel free to add any additional user or host based access restrictions here # (such as limiting users who can commit, this will not be covered here) </Location>
If you chose to setup multiple repositories, you will need to alter the ‘SVNPath /tmp/repos’ directive. Instead use ‘SVNParentPath /tmp’ to indicate that the /tmp directories contains multiple repositories. You will still need to specify the specific repository you are targeting in the url during a checkout (as well as the specific project in that repository less you get them all) but it saves you the hassle of setting up an apache directive for every repo.
svn co http://localhost/repos/foobar/trunk/foobarFrom there users with the necessary permissions can check in and perform the various other SVN operations.
Troubleshooting 1. SELinux: If you have SELinux enabled you will need to run the following command to grant additional privileges to httpd
chcon -R -t httpd_sys_content_t stuff
Thanks go to Michael Pechner for the tip
No such file or directory: The URI does not contain the name of a repository.
This indicates that you have used ‘SVNParentPath’ but did not specify the name of the repository. Apache will not allow anyone to view all the repositories it is hosting.
Could not open the requested SVN filesystem
And inspecting the apache error log, we see:
(20014)Internal error: Can't open file '/tmp/repos/foobar/format': No such file or directory
This indicates you miscorrectly used ‘SVNParentPath’ to specify a single repository. eg. you specified ‘SVNParentPath /tmp/repos’ in the apache configuration. This is what threw me off initially (and caused me to write this guide when I figured it out) as once again ‘repos’ is a single repository which we are simply using to store multiple projects. If you have ruled this possibility out, make sure apache has r/w access to all the repository files.
1. http://svnbook.red-bean.com/en/1.4/svn-book.html - The Bible for Subversion users / admins. Chapter 2, 5, and 6 contain the most useful info for setting up your own repo
2. Good guide to getting things setup