I know this thread is two months old, but it is the only reference in
the official Heroku channels I have found referring to the dsl
conflict with the 1.9.2 stack and rake 0.9.x (I resorted to SO to find
a few more thorough explanations and possible solutions). If
documentation exists it would be
That's a good point. We'll take a look at adding something here.
-Terence
On Thu, Jul 14, 2011 at 4:48 PM, Francois fhar...@gmail.com wrote:
Terence
this error has been happening to a lot of people, it might be worth
mentioning this in the docs somewhere? I searched for 'uninitialized
Rake 0.9.x no longer includes the DSL module in the top level
namespace. So another solution to the uninitialized constant
Rake::DSL problem is to explicitly include the DSL module in your
Rakefile, near the top, like this:
require rake
include Rake::DSL
It's more or less fixed now (with Rake
Hello Keenan,
It's because rake is built into ruby 1.9.2 and the version is 0.8.7 and
that's the one being called here. We're looking into ways to fix this. In
the meantime, can you try hard coding your rake to 0.8.7 in your Gemfile?
Once you have that working locally, it should work fine on
Terence
this error has been happening to a lot of people, it might be worth
mentioning this in the docs somewhere? I searched for 'uninitialized
constant Rake::DSL' in the docs and there was no mention.
- F
On Jul 14, 10:53 am, Terence Lee tere...@heroku.com wrote:
Hello Keenan,
It's because
Thank you for all your help.
I added rake and re-created on the cedar stack.
Specifying thin broke my local passenger, so I added a production group
gem 'rake', '0.8.7'
gem 'thin', :group = :production
Thank again,
Keenan
On Jul 14, 2011, at 5:48 PM, Francois fhar...@gmail.com wrote:
Hi,
Question: Are others able to run: heroku rake db:migrate OR heroku console
puts Model.count ?
This is probably user error, but I can't figure it out. reminds me of not
specifying RAILS_ENV when running rails console.
I had run rake db:seed which populated the Avatar model.
I view a page
