I'm open to suggestions about how to make this more useful. Dan, can you tell me more of what you're trying to do with the HOSTS environment variable, and what the behavior you expect is?
- Jamis On Oct 4, 2007, at 10:32 AM, Dan Powell wrote:
I can see how that might help with HOST restrictions where you want to change hosts in the middle, but here my restrictions are role based and the hosts for those roles are not changing at runtime. Based on Jamis' comment in that thread "If you set the HOSTS environment variable, all tasks will use it, instead of whatever hosts list they might have otherwise. " I even tried explicitly hard coding setting the ROLES variable, but that didn't really help anything. Perhaps that's a HOSTS vs ROLES behavior, I'm not sure. Should I try to set the HOSTS variable with the hosts for the ROLES I've specified? Again, I'm not changing HOSTS (or ROLES) in midstream, so I'm not sure why "changing" these variables to the same value as the one specified when invoking cap would help, unless there is some destructive processing done to the ROLES set on startup that I'm now having to override in my task. On Oct 4, 9:54 am, Joe <[EMAIL PROTECTED]> wrote:Dan,Seehttp://groups.google.com/group/capistrano/browse_thread/ thread/c4885d....Joe--~--~---------~--~----~------------~-------~--~----~To unsubscribe from this group, send email to capistrano- [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/ group/capistrano-~----------~----~----~----~------~----~------~--~---
smime.p7s
Description: S/MIME cryptographic signature
