I figured it out, I just added :norelease => true to the role definition.
Paul On 9/29/07, Paul Dowman <[EMAIL PROTECTED]> wrote: > > > That works when you explicitly define roles for all tasks, but how > can I make sure that default tasks like deploy:setup are not run > twice? > > Thanks, > Paul > > On Sep 19, 10:48 am, "Jamis Buck" <[EMAIL PROTECTED]> wrote: > > Just define the server multiple times withdifferentusernames, and > > then classify each task with the appropriate role: > > > > role :foo, "[EMAIL PROTECTED]" > > role :bar, "[EMAIL PROTECTED]" > > > > task :first_task, :roles => :foo do > > # ... > > end > > > > task :second_task, :roles => :bar do > > # ... > > end > > > > Note, though, that all hosts, regardless of username, must use the > > same password. That, or you must be using public keys (which is the > > recommended approach). > > > > - Jamis > > > > On 9/19/07, ky <[EMAIL PROTECTED]> wrote: > > > > > > > > > I have the same question; would like to bump this to the top again. > > > > > Is closing existing connections the best way to connect to a host as a > > >differentuser, and if so, what's the best way to do that? > > > > > -- http://pauldowman.com --~--~---------~--~----~------------~-------~--~----~ To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/capistrano -~----------~----~----~----~------~----~------~--~---
