You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
And have put the following in my config/deploy.rb:
cloud_roles :app, :solr
But when I execute the following command, capistrano only connects to the solr instance, not to both:
cap app solr shell
* 16:10:56 == Currently executing `app'
* 16:10:56 == Currently executing `solr'
* 16:10:56 == Currently executing `shell'
cap> date
[establishing connection(s) to <server2-ip>]
Similarly, when I reverse the order (cap solr app shell), it connects to server-1, so it appears that the roles are overwriting each other rather than being additive.
And then simply calling cap shell works as desired, but the documentation describing this configuration has a warning about this not working with load balancers, so I'm not sure if this is the correct approach.
The text was updated successfully, but these errors were encountered:
Great catch. I believe that the :options => { :default => true } should be set to all cloud_roles, so capify-cloud would be a drop-in gem for avoiding manually writing roles on your Capistrano configuration.
I have the following ec2 setup:
And have put the following in my config/deploy.rb:
But when I execute the following command, capistrano only connects to the solr instance, not to both:
Similarly, when I reverse the order (
cap solr app shell
), it connects to server-1, so it appears that the roles are overwriting each other rather than being additive.As a workaround, I can use the following config:
And then simply calling
cap shell
works as desired, but the documentation describing this configuration has a warning about this not working with load balancers, so I'm not sure if this is the correct approach.The text was updated successfully, but these errors were encountered: