My recommendation: keep the host names distinct, and just use roles to indicate different purposes of identical hosts. Thus, you'd have "host1" in both the app and loadbalancer roles.
Personally, I've used the fact that Capistrano does NOT resolve host names early. It's great for testing recipes, demoing (and debugging) Capistrano, etc. I'd hate to see that go away. - Jamis On Wed, May 27, 2009 at 5:45 PM, Christian van der Leeden <[email protected]> wrote: > > Hi, > > we're deploying on EC2 and to keep the setup clean we've defined host > aliase names. > E.g. app1 and app2 for the app servers, lb1 for loadbalancer 1 etc. > > Even though the names are different the hosts are sometimes the same. > E.g. load balancer > is also hosting the app server 1. On a deploy the code deploy would > now run in parallel > on the same host (lb1 and app1 who are identical). > > I'm looking for ideas on how to patch (or configure) capistrano to > prevent this situation. > > I imagine something along the lines of resolving the hostnames before > running a command > and then filtering out the duplicates. Is there an easy way to do > accomplish this? > > Thanks > > Christian > > > > > --~--~---------~--~----~------------~-------~--~----~ 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.co.uk/group/capistrano?hl=en -~----------~----~----~----~------~----~------~--~---
