Rails :(
I’m once again reminded of why I really hate Ruby on Rails. Everytime I’m programming a web application in the environment, I’m thinking to myself something alongs the lines of “yeah, yeah, yeah! this is totally the greatest thing ever!” Then comes time to deploy the fucking thing. I know, I know: I should be using a Mongrel cluster to serve my Rails apps and Apache running mod_proxy to serve static content. That’s what I should be doing. However, I don’t have the money to drop on the kind of dedicated hosting it would take to do that and, frankly, I don’t have the time to configure everything about the box on which this ideal Ruby on Rails installation would live. I’ve already had to configure an email server once in my life (and that was one time too many).
So, sadly, I’m stuck with Dreamhost and their “we only use Apache” policy. Frankly, I can understand the desire to only use one web application to serve your content. It makes logical sense (something that I find isn’t true about a lot of Ruby (I’m looking at you, Simply RESTful)). Why should I, really, have to support at least two (but sometimes three or four) programs to serve Rails? It’s not that good … or is it?














