Update: buzzco was using this and there needed to be some formatting and content changes to make it more useful. So here is the new and improved runlog.
Ok, since no one asked, here is the runlog of what I did to actually set up my svn repository and WebSVN. Note that I now have a repository of a single repository. This assumes that at some point I’ll have some other code to release or at least host.
Setting up svn
First create a user/group svnowner to own the repository and for other stuff that i’ll explain later.
Ok, here we are going to create a repository unsure which will hold the rest of the repositories. Under this repository we will have 2 more. The first we will add right away. The second I will add after as an example or maintaining this type of setup.
Create these where you would like your repositories to live. I placed mine in /home/svnowner/
svnadmin create unsure
svnadmin create unsure/bluecheese
Now we must create a temporary directory to hold the svn repository structure and your source code for the initial import (if there is any). This will be removed later so it can go anywhere, I set it up in /tmp/
mkdir bluecheese
mkdir bluecheese/tags
mkdir bluecheese/branches
Now move your source into the bluecheese/trunk directory. Then import that code along with a commit log to your main repository. This will create the unsure/bluecheese module.
mv source/ bluecheese/trunk
svn import bluecheese file:///home/svnowner/unsure/bluecheese -m ‘Initial import of fromage code’
We now have to change the permissions on the repository for 2 reasons. You have a new group svnowner to place the repository in anyway. We will add the user apache runs as (www-data on debian, apache on gentoo, etc) and whatever users you want to be able to check this source out and in (your developers).
chgrp -R svnowner /home/svnowner/unsure/bluecheese
chown -R svnowner /home/svnowner/unsure/bluecheese
chmod -R g+w /home/svnowner/unsure/bluecheese
To make things pretty and more transparent to users let’s create a /svnroot directory and symlink it to our main repository. Also if we ever change the location of our repository we can just recreate the symlink and anything that refrences that should be set.
ln -s /home/svnowner/unsure/ /svnroot/
Setting up WebSVN
http://websvn.tigris.org/
In WebSVN/include/config.inc uncomment and edit the following line
$config->parentPath(”/svnroot/”);
Adding another source tree
Screw, this has been a lot of typing. Basically copy the steps for ‘bluecheese’ verify your permissions. WebSVN should just work. If not leave a comment and I’ll clarify.
http://unsure.org/svn
BANG.
