Looks like a pretty delicate hack to me, and that whilst this stuff lives in the same repo, it's deployed to different servers, in different configurations. In Ruby land, that's a smell that your repos are merged, and you should break them out.
One of the overriding philosophies of Capistano is that a deploy should be atomic and repeatable… so "I want to deploy bits and pieces at various times, to various places" will always be a kludge. In future versions the Capistrano core is being reduced to a selection of useful helpers, with sane scaffolding and defaults, this should lead to a situation where it's significantly easier for you to build what you need, without having to deal with so much nonsense. - 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
