Just something else to note that we have seen, is that after running a
migration we have had to *issue a restart* to correct odd behaviour with the
new or changed table column.
On Tue, Aug 9, 2011 at 6:42 AM, John Beynon j...@beynon.org.uk wrote:
This isn't something that has affected myself
I redeployed an app today, and started getting a You have already activated
rack 1.3.2, but your Gemfile requires rack 1.2.3. Consider using bundle
exec. (Gem::LoadError)
I have a rails 3.0.3 app, and according to my Gemfile
rails (= 3.0.3) depends on
rack (~ 1.2.1)
I looked back at my
ok, so after reading through everything I could find on this, I determined
the following:
1. While I have all my gems specified by bundler, I had a .gems file,
which until today wasn't causing any issues, but once I removed it, and
ensured that heroku was loading my gem properly, it was
