Image of the glider from the Game of Life by John Conway
Skip to content

WordPress SVN

I recently decided to reinstall my WordPress blog with the SVN copy of the software. Because WordPress does not support upgrading through the default install- a major hindrance, I've decided to keep my copy updated through SVN. This means that you need a working copy of SVN on your server. If running Ubuntu/Debian, the following command will get it installed (assuming your account is added to the /etc/sudoers file:

aaron@kratos:~$ sudo aptitude install subversion

Once installed, all you need is to get the latest copy to your server in the directory that you plan on serving it from. For example, if you plan on serving it from /var/www (also, assuming your unprivileged account has write access to /var/www):

aaron@kratos:~$ cd /var/www
aaron@kratos:/var/www$ svn co

Now you have the latest copy of WordPress running on your server. Configure your web server daemon as needed to serve PHP files from that directory. When ever you need to upgrade, just issue an 'svn update' on that base directory:

aaron@kratos:/var/www/trunk$ svn update

There you have it, the latest and greatest running copy of WordPress. Of course, it should be warned that this is the unofficial release of the software, and bugs may exist causing problems with plugins and serving the software. However, if you are willing to take the punches, then I would recommend running the SVN copy to keep your WordPress insall up-to-date. Until the WordPress devs decide it's important enough to add an upgrade utility in the software directly, this is definitely the best approach I think.

{ 4 } Comments

  1. Karol Krizka | December 9, 2007 at 11:46 am | Permalink

    Why not just use one of the upgrade plugins, like the One Click Update. It does everything for you, including downloading the new version and backup of your database.

  2. Bruno | December 9, 2007 at 12:21 pm | Permalink

    Or WPAU. 🙂

  3. Aaron | December 9, 2007 at 1:46 pm | Permalink

    3rd party plugins are great and all, but why aren't we seeing this upgrade functionality built right into the software? Why rely on a 3rd party tool? Luckily, SVN is an easy way to do things, and it's coming down the pipe from the official devs. So, I guess seamless upgrades are on their mind at least a little.

  4. Joseph Scott | December 9, 2007 at 5:32 pm | Permalink

    I agree that subversion makes it pretty easy to stay up to date. I wouldn't recommend that regular folks run a production blog from -trunk though. While code from -trunk generally runs fine, that isn't always the case.

    As for the upgrade issue, PHP in general and WordPress specifically run under a variety of conditions. Making one upgrade feature that works under all of those conditions isn't going to happen. Beyond that, a built in upgrade feature would increase the security risk because your web server would need write access to the WordPress source files running your blog.

Post a Comment

Your email is never published nor shared.