The deploy task doesn't appear to do any filtering, so when I deploy, Capistrano tries to deploy application code to my load balancers.
I tried doing something like this:
before "deploy", "do_filter" do
set :filter, role: %w[app work]
end
But it still deploys code to my servers tagged with the "web" role.
I know that I can do this:
ROLES=app,work cap production deploy
But that is a pain.
It seems very reasonable to put in the configuration the idea of "all tasks within the deploy namespace should affect servers with [these] roles". In fact, most Capistrano plugins do something like this; they give you a variable to set which restricts tasks to a certain role or roles.
Why doesn't the out of the box "deploy" namespace do something like this?
Thanks,
-- C