First, check to make sure that rake is mentioned in your Gemfile. If it’s not, add it, and specify the version “you already activated”. Then, you’ll need to tell bundle to update the rake version it’s using for your app: bundle update rake It’ll update your Gemfile.lock for you.
As explained in mordaroso’s answer, there is a problem in Rake 0.9.0. You need to temporarily downgrade Rake in order to avoid it: run: gem uninstall rake -v 0.9 (add sudo unless you use rvm) add to your Gemfile: gem ‘rake’, ‘~> 0.8.7’ and then run: bundle update You can skip the first step, but … Read more
Rake 11.0.1 removes the last_comment method which Rails 2.3 rspec-core (< 3.4.4) uses. Therefore until/if a patch is released we need to pin rake to an older version in Gemfile: gem ‘rake’, ‘< 11.0’ then: $ bundle update $ grep rake Gemfile.lock rake rake (>= 0.8.7) rake (10.5.0) rake rake (< 11.0) We are now … Read more
You can get access to your models, and in fact, your whole environment by making tasks dependent on the environment task. This lets you do things like run rake RAILS_ENV=staging db:migrate. See “Custom Rake Tasks”.
It was deemed a “security” risk. You can get around it by using absolute paths File.expand_path(__FILE__) et al or doing require ‘./filename’ (ironically). or by using require_relative ‘filename’ or adding an “include” directory ruby -I . … or the same, using irb; $irb -I .
NOTE: This doesn’t run the test via rake. So any code you have in Rakefile will NOT get executed. To run a single test, use the following command from your rails project’s main directory: ruby -I test test/unit/my_model_test.rb -n test_name This runs a single test named “name”, defined in the MyModelTest class in the specified … Read more
A tweet from DHH earlier. Rake .9.0 breaks Rails and several other things, you need to: gem “rake”, “0.8.7” in your Gemfile.
For starters rake db:rollback will get you back one step then rake db:rollback STEP=n Will roll you back n migrations where n is the number of recent migrations you want to rollback. More references here.
Just to follow up on this old topic; here’s what I think a current Rakefile (since a long ago) should do there. It’s an upgraded and bugfixed version of the current winning answer (hgimenez): desc “Testing environment and variables” task :hello, [:message] => :environment do |t, args| args.with_defaults(:message => “Thanks for logging on”) puts “Hello … Read more
Figured it out, the task should look like: namespace :test do task :new_task => :environment do puts Parent.all.inspect end end Notice the => :environment dependency added to the task