NotRocketSurgery: acts_as_pipe :web

acts_as_pipe :web

jd — Fri, 18 Aug 2006 21:31:00 -0400

This article has moved over to our sister spin-off blog, RubyJudo, which focuses on more arcane technical topics than NotRocketSurgery.

"acts_as_pipe :web" by Kit

Mon, 21 Aug 2006 14:05:10 -0400

Welcome, JD!

"acts_as_pipe :web" by Ryan Norbauer

Sat, 19 Aug 2006 20:15:22 -0400

In fact, I’m running Edge Rails and it uses Mongrel automatically with script/server by default. ;)

"acts_as_pipe :web" by JD

Sat, 19 Aug 2006 18:37:58 -0400

I personally moved my Typo install to a simple Mongrel + lighttpd 1.4.11 configuration using mod_proxy in “fair” mode, which while not very “fair” works fine for my minimal traffic. Doing so took me less time than to write this article about what I learned – amazingly painless. Adding Pound to this would be the way I recommend for anyone who wants to steer clear of the Apache barge.

What has been missing in my book is an official recommendation from the Rails team to use Mongrel, instead of relying on the blogosphere to say “do it this way.” I am suspecting that Mongrel will be strongly encouraged as well as better integrated with Rails in 1.2 (e.g., script/server support).

"acts_as_pipe :web" by Ryan Norbauer

Sat, 19 Aug 2006 13:51:57 -0400

Hi JD,

Welcome to NRS, and thanks for your first post.

At Lovetastic and right here on NotRocketSurgery, we’re currently using Apache 2.2 with mod_proxy_balancer + Mongrel + Rails + Capistrano for deployment.

There are several great tutorials on how to do this.

However, I can’t wait until Jan Kneschke releases the next version of Lighty with better a mod_proxy, which will work with Mongrel. I spoke with him at RailsConf and got the sense that he has this as his top priority, so there is hope of a release very soon. We’re already at the pre-release stage, so it’s very encouraging.

I had to work for about 5 or 6 hours to get Apache to work properly with my multiple virtual hosts, the mongrel clusters, etc. It was a mess, and terribly painful. Apache configs are no fun.

Lighty on the other hand is a breeze to configure, and the config files are both very concise and readable. We’ll be switching back to Lighty at the very first possible opportunity.