Integrated support for Traefik reverse-proxy setup #27
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Reason for this PR
We recently added support for the reverse-proxy Traefik to the registry. The setup with Traefik allows users and applications to connect to instances deployed inside a docker container. Instead of directly connecting to the requested instance, the users / applications can connect to the Traefik-Host, and specify the additional header
Host: <unique-host-string>, which will relay them to their actual target.The WebApp has to decide whether or not it can connect using IP and Port (when both instances are inside the Docker network, or when the WebApi is outside Docker) or using Traefik (when WebApi is inside Docker network and WebApp is not).
Changes in this PR
TraefikConfigwhich contains the unique host string assigned to the instance by Traefik.