So I’ve spent this week moving our company hosted SVN from Beanstalk to Springloops. I feel I’ve been swinging between hell and zen, but the learning has been awesome. As a summary of what I’ve found I thought I’d give a quick walk through how I did it.

Most of this stuff was the usual dump/load cycle, but there are a couple of things which needed some extra attention.

Firstly, both Beanstalk and Springloops have the ability to export and import SVN dumps via easy-to-use web interfaces. This really could be as easy as download, upload. Try that first.

We had a couple of problems though. Previously we had a mishmash of company repos and project repos; these had to be merged and sorted. We also had different usernames on each system(!) which meant that during an import previous commits were not matched to current system users.  The author attribute needed to be updated for all previous revisions.

This was all done on OS X, but should be applicable to any Unix-like with the appropriate libraries, etc.  So we’ve got our dump from Beanstalk, now we just need to create a local repository to do our work on (always work on a backup!!).

$ svnadmin create --pre-1.4-compatible newrepo

We use the pre 1.4 compatible flag to overcome files system changes within SVN between versions. These changes can potentially cause errors (svn: Expected FS format ’2′; found format ’3′) when propset-ting revision histories, in my case, author/committer names.

Next job, import your dump file.

$ svnadmin load newrepo < dumpfile

If you’re looking to do the merging, as I was, then you want to make yourself a directory in your repository (usual ‘svn mkdir’ commands) and then load it in the following fashion:

$ svnadmin load newrepo --parent-dir myfolder < seconddumpfile

Ok, we’ve done our merging, now we’re going to update our author histories.  Now the SVN manual gives you information on doing this one version at a time with a propset.  It also talks about other recursive actions such as deleting files, which isn’t our concern.  For changing authors, I found a tidy script called svn-author-tweak.py from CollabNet.

If you want to give your repository a check before you upload it, just checkout to a local test.

$ svn co file:///path/to/newrepo /path/to/test/repo

Once that’s done, dump the file.

$ svnadmin dump newrepo > my.dumpfile

Upload

???

Profit

Linux is ok on the desktop, but for servers, I really prefer FreeBSD.

Sometimes I get tired of that, and use NetBSD for a while. A short stint with NetBSD, Apache, Postgresql, and PHP usually refreshes me long enough so that I can FreeBSD, Apache, Postgresql, and PHP again.

Firstly I’d like to point to the post that originally helped me do this at webmasterview.com.

Now, time to open up our trusty terminal. It is possible to do this through synaptics, but its quicker to do it like this:

First thing is to install mysql for databases on our machine. Copy this bit of code into your terminal:

sudo apt-get install mysql-server

Next we need apache2 as our webserver. Here is the code:

sudo apt-get install apache2

Then we need to get php:

sudo apt-get install php5

There are our three basic components. Now we need to hook them together:

sudo apt-get install libapache2-mod-php5

and

sudo apt-get install php5-mysql

Now that’s just grand. We’ve now got all the elements that we need to serve files to the net. The thing is, we’re only doing this so we can work on stuff at home, in which case what we’re really looking for is an easier way to do so. What we need to do is have a public_html folder in our user directory. Perhaps now would be a good time to do that. The next step is making that work on the webserver we’ve just installed. Run this snip of code:

sudo a2enmod userdir

Then restart apache:

sudo /etc/init.d/apache2 force-reload

You should now be able to reach your home folder via http://localhost/~yourusername/

Finally we want to be able to administer our mysql databases. Though there are many good tools for doing this I still go back to the web based phpMyAdmin. Apart from the fact that it’s highly automated (which suits me just fine) it’s also a very common program to find on your paid hosting, so would also be very familiar when you go live. For the quick and dirty way of getting it up and running, download phpMyAdmin and extract to your public_html folder. Personally I rename it to something a little easier. Then rename the file within from config.example.inc.php to config.inc.php and within that file put something in the blowfish_secret field. Then all you have to do is navigate your browser to something like http://localhost/~yourusername/phpMyAdmin

addendum

If your server is going to be visible from the big bad world and this is your everyday machine then you need to turn off that user public_html stuff (it’s insecure for general use!). To do that just enter this instruction

sudo a2dismod userdir

then reload apache as before