Rails core team decided to have consistency by enabling rails command to support everything that rake does. For example in Rails 5 commands like db:migrate, db:setup, db:test etc which are part of rake command in Rails 4 are now being supported by rails command. However you can still choose to use rake to run those … Read more
For this particular task, you only need to change the DB connection, so as Adam pointed out, you can do this: namespace :db do namespace :test do task :reset do ActiveRecord::Base.establish_connection(‘test’) Rake::Task[‘db:drop’].invoke Rake::Task[‘db:create’].invoke Rake::Task[‘db:migrate’].invoke ActiveRecord::Base.establish_connection(ENV[‘RAILS_ENV’]) #Make sure you don’t have side-effects! end end end If your task is more complicated, and you need other aspects … Read more
I agree with ddfreynee, but in case you know what you need code can look like: require ‘rake’ Rake::Task.clear # necessary to avoid tasks being loaded several times in dev mode Sample::Application.load_tasks # providing your application name is ‘sample’ class RakeController < ApplicationController def run Rake::Task[params[:task]].reenable # in case you’re going to invoke the same … Read more
A little bit more explicit, in your \config\deploy.rb, add outside any task or namespace: namespace :rake do desc “Run a task on a remote server.” # run like: cap staging rake:invoke task=a_certain_task task :invoke do run(“cd #{deploy_to}/current; /usr/bin/env rake #{ENV[‘task’]} RAILS_ENV=#{rails_env}”) end end Then, from /rails_root/, you can run: cap staging rake:invoke task=rebuild_table_abc
Put this in your Rakefile above require ‘rake’: require ‘rake/dsl_definition’
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
If you need the task to behave as a method, how about using an actual method? task :build => [:some_other_tasks] do build end task :build_all do [:debug, :release].each { |t| build t } end def build(type = :debug) # … end If you’d rather stick to rake‘s idioms, here are your possibilities, compiled from past … Read more
I’ve used the extremely popular Whenever on projects that rely heavily on scheduled tasks, and it’s great. It gives you a nice DSL to define your scheduled tasks instead of having to deal with crontab format. From the README: Whenever is a Ruby gem that provides a clear syntax for writing and deploying cron jobs. … Read more
You can specify formal arguments in rake by adding symbol arguments to the task call. For example: require ‘rake’ task :my_task, [:arg1, :arg2] do |t, args| puts “Args were: #{args} of class #{args.class}” puts “arg1 was: ‘#{args[:arg1]}’ of class #{args[:arg1].class}” puts “arg2 was: ‘#{args[:arg2]}’ of class #{args[:arg2].class}” end task :invoke_my_task do Rake.application.invoke_task(“my_task[1, 2]”) end # … 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.