Cap 2 - custom tasks in Capfile, only variables in deploy.rb?

[Wes Gamble]

I just read somewhere online that custom tasks should be in the Capfile
and just the configuration parameters should be in the deploy.rb file.

Coming from 1.4.1, my custom tasks are in the deploy.rb file.

Does it really matter? Should I move my tasks into the Capfile?

Thanks,
Wes

[Jamis Buck]

It doesn't matter. If you're using cap for Rails deployment, I'd keep
all of your tasks in config/deploy.rb for consistency's sake.

- Jamis

> --~--~---------~--~----~------------~-------~--~----~
> To unsubscribe from this group, send email to capistrano-...@googlegroups.com
> For more options, visit this group at http://groups.google.com/group/capistrano
> -~----------~----~----~----~------~----~------~--~---
>

[David Masover]

Depends if you're doing multiple Rails apps. In that case, if you have a lot of common tasks, it makes sense to separate them from app-specific configuration (which does belong in deploy.rb.)

I'm not convinced that doing multiple rails apps is easy for anyone, though.

In either case, this is a design choice, not a technical one. Capistrano doesn't know about deploy.rb anymore, it just knows about the Capfile. It's just that the default Capfile loads deploy.rb, at which point, there's really no difference between th etwo.