LolocoJr » typo

Typo -> Mephisto -> WordPress

andy — Wed, 21 Jan 2009 16:19:01 +0000

First I tried Typo, then Mephisto and now this blog is running WordPress. As a Ruby fan I really wanted to use Ruby everywhere, 2 years ago. I’m now at the point where I just want working stuff (kids will do that to you I guess). The migration from Mephisto to WordPress was very very smooth, thanks to this excellent article. The Mephisto version I was running was producing a Rails error based on some spam message which was posted. I really didn’t want to dig into the error and upgrading to the latest Mephisto was going to be quite a bit of work. All in all the switch to WordPress took about 2 hours in total, including customizing the theme a bit and making sure the old permalinks kept working. Cool!

Typo on Lighttpd

andy — Sun, 15 Jan 2006 21:28:00 +0000

This blog has been running on lighttpd since last week. So far it seems to be the best setup for running Rails app. Of course everyone in the Rails world alread knew this but breaking the Apache habit after 8 years is quite hard. However, I’m convinced now that Rails on top of lighttpd + fastcgi is, at least for me, currently the best deployment stack for production use. I’ve already switched one of our internal Rails app to the same app. Currently testing, the soon to be deployed, commercial project and it’s been smooth sailing so far! Perhaps it’s time to try SCGI again.

Apache2 + SRR = Crash and Burn?

andy — Mon, 09 Jan 2006 22:39:00 +0000

Well, it turns out Apache2 + SCGI is not a good match, at least not the way I set it up, by following all the (scarce!) documentation on the subject. I used the SCGI Rails Runner package for running. The benefits of having better control of the Rails processes and the supposed easy clustering setup sounded quite appealing. However I hit a brick wall quite quickly. While attempting some load tests on a new Rails that is going into production somewhere this month I noticed the scgi process hung reliably after only 3 concurrent requests! The only thing I could find in the logs were this:

Errno::ECONNRESET (Connection reset by peer)

After the above error is thrown the connection between Apache2 and scgi is lost and your Rails app is dead in the water (Apache 2.0.54, mod_scgi 1.0, SRR 0.4.3, Rails 1.0, Ruby 1.8.3). Perhaps Ruby 1.8.3 is to blame? I hope Breezy upgrades to 1.8.4 (not likely), Dapper is still a nono, so probably have to self-compile Ruby. Will try this over the weekend. In the meantime I’m testing lighttpd + fastCGI and so far: WOAW!! More on this later..