Passenger 2.0.6 is not compatible with Rails 2.3.1
Ryan Schwartz thinks I should actually use this blog of mine once in a while. Well, that makes one of us ;)
However, consider this a public service announcement for all those people who might have run into the problem I did with Rails and Passenger (modrails) compatibility.
An introduction before we begin: 99% of the time I use mongrel in development, because that’s what I use in production and that’s what has become my habit. However, for a new project I’m working on, we’ve discussed trying Passenger in production. So, more recently, I’ve been using passenger some in development for that project (I still, out of habit spin up script/server when starting work in the project).
As of a few days ago, this new project was running Rails 2.2.2 with Passenger 2.0.6 (when I remembered to got to http://go.local instead of http://localhost:3000). However, always wanting the apps I’m developing to stay up to date with the current version of Rails, I upgraded one to the latest, greatest Rails 2.3.1RC. A few Rails compatibility / deprecation issues, but everything was still working just fine—or so i thought. I didn’t notice anything strange because I was still developing with mongrel; I would still spin up script/server and hit http://localhost:3000. Late last night though, I remembered to use my passenger virtual host, and the following error pops up:
Ruby on Rails framework version 2.3.1 seems to be corrupted?! Please reinstall it?! Wha??
Anyway, it was a little frustrating as I tried a number of things to fix it, but the ultimate solution was simple: upgrade to Passenger 2.1.1, and voilá! Everything’s fixed.
The end.
Posted by Phil Burrows on Mar 12, 2009
Hello
I've passenger 2.2.2, rails 2.3.2 and all my apps on development code are starting very slowly. I know, that in dev mode server will again load all libs, plugins, but passenger 2.0.6 was very fast, I dont know where to look for any optimazation or sth. Any ideas?