Rails 2.3 vs. Passenger 2.0.6

software development


I am using Rails 2.3 (vendor’ed to my app) on DH and having problems with DH’s Passenger 2.0.6. There is a known problem with “Set-Cookie” in Passenger 2.0.6 (fixed in 2.1.1) but DH won’t be upgrading Passenger anytime soon :frowning: so I’m feeling a bit stuck.

Does anyone have any suggestions on how I might be able to make this work? I’m thinking of:

  1. Switching to DreamHost PS ($$) so I can run a 2.3-compatible Mongrel instead (anyone have thoughts on that option?)

  2. Switching from Passenger to the “old” fcgi deployment (but will that really help my problem? Can I select my own mongrel/webrick version in this scenario)?

  3. Or is there some magical way for me to “vendor” my own Passenger so I can deploy my own 2.1.1 instance?

Apologies in advance if this is a silly question - but I really would appreciate any wisdom out there!


I have the same problem, and for now I’m using method 2 (FastCGI). Unfortunately, I can’t think of any way around this.

Let me know if you find any answers.


I feel with you. I think Dreamhost’s sluggishness in maintaining Rails (one of their biggest assets) is a shame. Rails 2.3 is a long awaited release that solves many problems. It requires Passenger 2.1.2 according to DHH: http://weblog.rubyonrails.org/2009/3/16/rails-2-3-templates-engines-rack-metal-much-more

Did they say they “won’t be upgrading Passenger anytime soon”? If that is the case, I think I’ll have to look for a better host.


They were very polite about it, but gave no timeframe and mentioned that it has lots of config changes for them, so it wasn’t trivial.

I’ve since moved the app over to my own VPS at SliceHost. I still like DH a lot, but just couldn’t wait. I also need a bit more control and performance for when the app goes live.


It seems now they’re working on a Passenger/Rails update. At least it’s in “Suggestions We’re Working On”. I hope it won’t be the same barren run over again when Rails 3 comes out later this year.