Thanks, Rodney. Although this is my attempt to use Capistrano for something
other than a Rails deployment, I'm not sure why I never encountered this
limitation with one of the more complicated Rails apps I've worked on. It
seems to me a real defect, one that ought to be fixed in Cap itself.
Roger,
This query comes up time and time again, should they inherit, or not - I
think sadly there's no good answer, except to make it configurable (which
leads to a much less clean API), I'd really welcome some input, and would be
happy to help you write a decent patch, so that we can settle it
Can someone reiterate the problem?
I've lost track of what you are trying to solve.
I applaud y'all for not keeping the whole thread in the reply, but do try to
keep some of the previous context.
On Oct 24, 2011, at 2:38 AM, Roger Rohrbach ro...@ecstatic.com wrote:
Thanks, Rodney.
Donovan, the problem is as such I believe:
task :a, :roles = [:alpha, :beta] do
b
end
task :b, :roles = [:charlie] do
# When A calls me, should I run against
# [:alpha, :beta] or [:charlie]
end
Roger, did I understand you correctly?
--
* You received this message because you are
Thanks Lee,
The problem is even more profound; I know what capistrano does in this
situation :charlie; but what I think it should do is additively filter the
roles;
So that in your example it would run on [] since you effectively said:
(:alpha || :beta) :charlie
Unless you had something
