Capistrano 3, using upload! in a task in lib/capistrano/tasks

Question

I'm using Capistrano 3 and I want to create my own task. So I created a file my_new_thing.rake in lib/capistrano/tasks and I can see the task when I run cap -T. But... some of the methods aren't available. When I try to use upload! I get

cap aborted!
NoMethodError: undefined method `upload!' for main:Object

But if I move the same task into config/deploy.rb then then upload! method is available.

So what's going on? How do I create new Capistrano tasks put them in separate file and have them work?

score 16 · Answer 1 · answered Aug 28 '14 at 21:24

16

I had the same problem, I created my own recipe in a separate file which I loaded in deploy but couldn't get upload! to work.

What fixed it for me was adding a role filter inside the task making my final recipe look something like this:

 namespace :figaro do      
   desc "Transfer Figaro's application.yml to shared/config"
   task :upload do
     on roles(:all) do
       upload! "config/application.yml", "#{shared_path}/config/application.yml"
     end
   end
 end
 before "deploy:check", "figaro:upload"

I hope that helps!

answered Aug 28 '14 at 21:24

David Svensson

558
4
15

1

The on roles check was everything I needed. Thanks. +1 – Brad Gunn Oct 06 '14 at 01:04
I had to add `execute "mkdir -p #{shared_path}/config"` just before the `upload!` line as that directory didn't exist on the server yet. – Brendon Muir Feb 29 '16 at 06:42

Arctodus · Answer 2 · 2014-07-05T13:57:45.560

1

You can create a folder config/recipes for your capistrano recipes if you want to keep them in separate files.

Use the .rb extension since this isnt a regular rake task.

In config/deploy.rb add this line

load File.expand_path('../recipes/my_new_thing.rb', __FILE__)

edited Jul 05 '14 at 13:57

answered Jul 05 '14 at 13:18

Arctodus

5,743
3
32
44

score 0 · Answer 3 · answered Jul 05 '14 at 13:24

If you want to use the rake tasks then you will need to create a task in the deploy file which calls that rake tasks which is not that smart of a move. So as @Sharagoz suggested the best route will be to create your own recipe file and include that in.

Capistrano 3, using upload! in a task in lib/capistrano/tasks

3 Answers3