How do I run a rake task from Capistrano?

Run("cd #{deploy_to}/current && /usr/bin/env rake `` RAILS_ENV=production")` Found it with Google ananelson.com/said/on/2007/12/30/remote-... The RAILS_ENV=production was a gotcha -- I didn't think of it at first and couldn't figure out why the task wasn't doing anything.

Run("cd #{deploy_to}/current && /usr/bin/env rake `` RAILS_ENV=production")` Found it with Google -- ananelson.com/said/on/2007/12/30/remote-... The RAILS_ENV=production was a gotcha -- I didn't think of it at first and couldn't figure out why the task wasn't doing anything.

2 A minor improvement: if you replace the semicolon with && then the second statement (running the rake task) will not run if the first statement (changing the directory) fails. – Teflon Ted May 12 '09 at 15:17 2 This won't work if you are deploying to multiple servers. It will run the rake task multiple times.

– Mark Redding Jun 3 at 20:36 1 one should really respect capistrano's rake setting "cd #{deploy_to}/current && #{rake} RAILS_ENV=production" – kares Jun 14 at 11:13 @Mark Redding: Could you put one of the servers in its own role for rake tasks and restrict your capistrano task to only run on servers with that role? – mj1531 Jun 24 at 15:25.

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.

1 better to use /usr/bin/env rake so rvm setups will pick up the correct rake. – DGM Nov 4 '10 at 20:30 With 'bundle exec' if available – Bogdan Gusiev Mar 18 at 14:20.

I personally use in production a helper method like this: def run_rake(task, options={}, &block) command = "cd #{latest_release} && /usr/bin/env bundle exec rake #{task}" run(command, options, &block) end That allows to run rake task similar to using the run (command) method. NOTE: It is similar to what Duke proposed, but I: use latest_release instead of current_release - from my experience it is more what you expect when running a rake command; follow the naming convention of Rake and Capistrano (instead of: cmd -> task and rake -> run_rake) don't set RAILS_ENV=#{rails_env} because the right place to set it is the default_run_options variable. E.

G default_run_options:env = {'RAILS_ENV' => 'production'} # -> DRY!

If the Rake task requires user interaction, it will not work.

Here's what I put in my deploy. Rb to simplify running rake tasks. It's a simple wrapper around capistrano's run() method.

Def rake(cmd, options={}, &block) command = "cd #{current_release} && /usr/bin/env bundle exec rake #{cmd} RAILS_ENV=#{rails_env}" run(command, options, &block) end Then I just run any rake task like so: rake 'app:compile:jammit.

This also works: run("cd #{release_path}/current && /usr/bin/rake ", :env => {'RAILS_ENV' => rails_env}) More info: Capistrano Run.

1 {deploy_to}/current won't work here. The symbolic link has not changed. If you update the rake task , this will run old code.

Consider using {release_path} instead. – Mark Redding Jun 3 at 20:35.

I have no idea how capistrano works, but just for the record -- this is the syntax to invoke a rake task from Ruby: Rake::Task"task:name".invoke.

– Benjamin Oakes Jun 29 '10 at 13:29 I didn't downvote you but it's probably because that doesn't work within Capistrano. – rfunduk Jul 27 '10 at 19:15.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.