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 all good. This article got me on the right track http://devcenter.heroku.com/articles/gem-dependency On Sun, Sep 4, 2011 at 6:05 PM, John McCaffrey <[email protected]>wrote: > 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 Gemfile.lock, between these deployments, and rack has > been set to 1.2.1 the whole time. > > Did something change? is there a way to execute a bundle exec command on > the bamboo stack (I know you can on cedar, but I'm in the middle of pushing > out a release and don't want to start messing with Cedar yet) > > -- > Thanks, > -John > > -- Thanks, -John -- You received this message because you are subscribed to the Google Groups "Heroku" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/heroku?hl=en.
