Oh, I see what you were saying. Yes, specifying ROLES or HOSTS as environment variables will override the restrictions for all tasks that get executed, not merely the top-level task.
- Jamis On 9/12/07, matt <[EMAIL PROTECTED]> wrote: > > I originally had just HOSTS and had the same problem, so figured I'd > add in the ROLES my HOSTS server was in to see if that helped. No go. > > Matt > > On Sep 12, 3:54 pm, "Jamis Buck" <[EMAIL PROTECTED]> wrote: > > You have to restrict either by ROLES or by HOSTS, but not both. > > > > - Jamis > > > > On 9/12/07, matt <[EMAIL PROTECTED]> wrote: > > > > > > > > > If I execute something like: > > > > > ROLES=web HOSTS=web01 cap deploy:start > > > > > the start_search task gets executed even though it is tied to > > > the :search role. This doesn't happen if I don't restrict the scope > > > using ROLES/HOSTS. Any workarounds known for this? > > > > > The relevant parts of my deploy.rb are: > > > > > role :web, "web01", "web02" > > > role :search, "search" > > > namespace :myns do > > > before "deploy:start", "myns:start_search" > > > > > task :start_search, :roles => :search do > > > end > > > end > > > > > --~--~---------~--~----~------------~-------~--~----~ To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/capistrano -~----------~----~----~----~------~----~------~--~---
