Article

Rails sure is weird sometimes.

Managing hundreds of Rails apps gives us the opportunity to see all of the amazing ways that Ruby and Rails can misbehave. I had an experience so weird last night that I think it deserves its own blog post. An app that hadn't been deployed in two weeks all of a sudden returned a 500 error for the URL we use to monitor it. Looking at the error, Passenger couldn't find the Rails gem. This is a 2.3 app, and doesn't use Bundler yet, so... this was weird. I've been working with Rails for almost 8 years now and have never seen this before in an app that hadn't been deployed to recently. I could understand if you changed the RAILS_GEM_VERSION line in environment.rb but hadn't actually installed that version of Rails, but that didn't happen in this case. What did I do? First, I tried the console to see if that could find the rails gem. It worked fine. Having proved to myself that ...

Full article: http://railsmachine.com/articles/2013/02/21/30-minutes-in...