> > Why is this…
Because Capistrano expects (reasonably, I believe) that all your servers have the same code deployed, failed deploys clean themselves up, and if you're adding machines to the cluster, you aught to be doing it in a way that makes them consistent with the existing node in the cluster. … and is there a workaround to force it to check all servers that are > supplied to the task? https://github.com/capistrano/capistrano/commit/a35da47da333f0518d23d2f6d2288a618b4d8affwas recently merged, and is as-yet unreleased, please examine the resulting code and see if that solved your problem, you can always use Capistrano directly from the Git repository via your gemfile. - Lee -- * 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.com/group/capistrano?hl=en
