bbPress: If only I needed a forum!

I admit it: I love Automattic. From WordPress to Akismet to Gravatar, I enjoy using their software and am continually impressed by the quality and elegance of the experiences they create. More than just about any other company, Automattic seems to live up to their motto: "Code is Poetry". So when they came out with bbPress I thought, "wow, there's something I really don't need." Which means, of course, that I eventually downloaded it and installed it on my server.

the download is freakishly tiny: about 336KB in Tar.gz format. Unpack that, send the files to the server, then run through a setup similar to the WordPress 5-minute install, with the noticeable absence of directly editing any database config files. It appears that BBPress writes its own config.php, using information gathered during the install process. Roughly 5 minutes after you start you have your own forums.

The default theme is fine, but there are obvious changes to be made, like replacing the "bb" logo with your own logo, changing the color scheme, etc. Unfortunately, there aren't a whole bunch of premade forum themes out there like you see for WordPress. Fortunately, just about all the changes you want to make are possible via CSS.

Akismet works with bbPress; indeed you will find the whole admin interface looks very much like the WordPress admin area, which means that administration is easy as well.

Anyway, if you would like to see bbPress in action, feel free to check out my test forum. I won't guarantee that it will exist for any particular period of time, and it doesn't have any real reason for existance; maybe you all will think of one. Posts will be filtered and moderated by yours truly; whatever I say goes is gone. To that end, please refrain from profanity, vulgarity, abuse or netspeak; any of those are grounds for having your posts deleted--or worse-- having you marked as a "bozo". Just about anything else probably goes, however.

Subversion 1.5.1 in OSX

So I upgraded my Subversion server a few weeks ago, but didn't think about it, because I was working on existing projects that all belived that they were still working in svn 1.4.x working copies. So today, when I created a new project in a new repository on the server I was shocked that my trusty TextMate would throw an error when I tried to commit my changes to the new repository. The error message let me know everything I needed to know:

this client is too old to work with working copy.

At first I wondered why my Eclipse-based SVN clients weren't having this problem, but I figured they were using internal copies of SVN (true, by the way. They're both using SVNKit)
So: apparently TextMate uses the system SVN client, which only makes sense. Thus I needed to upgrade my system client. Three minutes on Google let me know that Collab.net hosts compiled binaries, and that all I needed to do was run the installer and I would be good. So I dutifully downloaded and ran the installer (found here) and then went back to the command line and typed svn --version and like magic... It was still showing Subversion v. 1.4. snooping around a bit showed that the new version was installed in /opt/subversion. Okay then. so I went to ~/ and edited .profile to include /opt/subversion on the path:
export PATH=/opt/subversion:$PATH
and closed and re-opened my terminal session, so that it would reload the .profile preferences.
Okay! so I ran svn --version again, and 1.4. was still there. So, going into /usr/bin I find the svn command for version 1.4.x and use

sudo mv svn svn.old

to rename it.
After that I ran svn --version again and was greeted with a cheery 1.5.1, and Textmate could commit changes to my repository again.

So, if you have the same problem, now you know how to solve it. Thanks!