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
{{ message }}
This repository has been archived by the owner on Apr 2, 2023. It is now read-only.
The registration of a service with Consul can include a service address (docs).
In my use case I have different docker containers, one for Consul (server and agent), one for my Dropwizard service with your dropwizard-consul bundle.
I opened an issue for consul-client by OrbitzWorldwide #106 in which they describe how it is possible to pass the service address as a parameter by using a registration builder.
If dropwizard-consul would adapt this, it would remove the restriction, that the Consul agent and Dropwizard service are running on the same machine (e.g. in Docker scenarios).
The text was updated successfully, but these errors were encountered:
The registration of a service with Consul can include a service address (docs).
In my use case I have different docker containers, one for Consul (server and agent), one for my Dropwizard service with your dropwizard-consul bundle.
I opened an issue for consul-client by OrbitzWorldwide #106 in which they describe how it is possible to pass the service address as a parameter by using a registration builder.
If dropwizard-consul would adapt this, it would remove the restriction, that the Consul agent and Dropwizard service are running on the same machine (e.g. in Docker scenarios).
The text was updated successfully, but these errors were encountered: