If you know ahead of time that a host will be down, just remove the server from your role definitions before running deploy. There really isn't any way to ignore connection errors in Capistrano right now, though, and I don't think there ought to be. If you know in advance that a host will be unreachable, and you want a deploy to succeed in spite of that, you should remove it from your roles definition. On the other hand, if you do NOT know in advance that a host will be unreachable, an error is appropriate when the deploy tries to connect.
- Jamis On Jun 5, 2007, at 7:38 AM, Fredrik wrote: > > When I have an application server that is down for one reason or > another deploy will throw an Errno::EHOSTUNREACH. I was just wondering > if someone can point me in the right direction of where to put rescue > code for this. I don't want the script to fail because of it. Sometime > we remove a server for maintenance, so I would like for it to continue > without this host. > > Thanks, > Fredrik > > > > --~--~---------~--~----~------------~-------~--~----~ To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/capistrano -~----------~----~----~----~------~----~------~--~---
