On Sun, Jan 30, 2011 at 5:05 AM, Lee Hambley <[email protected]> wrote: > -f is intended to specify a Capfile, the Capfile loads `deploy.rb` from the > gem, which is where deploy:check is defined.
Yikes. For quite a while I've been using e.g. $ cap deploy -f config/deploy_alternate.rb : to specify the deployment target, and that works fine. But you're saying that's just a fluke, and the fact that deploy:check and other variants fail is expected? Having to create 2 files instead of 1 -- Capfile.alternate, referencing config/deploy_alternate.rb -- doesn't seem very DRY... But OK, thanks for the clarification! -- Hassan Schroeder ------------------------ [email protected] twitter: @hassan -- * You received this message because you are subscribed to the Google Groups "Capistrano" group. * To post to this group, send email to [email protected] * To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/capistrano?hl=en
