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
When using a remote docker host from `DOCKER_HOST` auto-proxy assumes the detected containers on not on the same network as SWAG:
61
+
When using a remote docker host from `DOCKER_HOST` auto-proxy assumes the detected containers are not on the same network as SWAG:
62
62
63
63
* If the detected containers do not have the `swag_address` label set then the Host IP will be used.
64
64
* If the detected containers do not have the `swag_port` label set then auto-proxy attempts to find a mapped **host port** on the container and will use it based on **container port** in this order:
@@ -68,19 +68,19 @@ When using a remote docker host from `DOCKER_HOST` auto-proxy assumes the detect
68
68
69
69
### Subdomains and TLD
70
70
71
-
If a detected container does not have `swag_url` label set then the subdomain and TLD can be programmatically generated.
71
+
If a detected container does not have the `swag_url` label set then the subdomain and TLD can be programmatically generated.
72
72
73
73
The default TLD used in nginx [`server_name` directive](https://nginx.org/en/docs/http/server_names.html) can be set using `HOST_TLD`. This can also be set per-host using the syntax described in [`DOCKER_HOST` for `default_tld`.](#multiple-hosts)
74
74
75
-
The subdomain used for a container can optionally be modified to include the Host's `friendly_name` described in the `DOCKER_HOST` syntax by setting the `HOST_INSERT` to either `prefix` or `suffix`
75
+
The subdomain used for a container can optionally be modified to include the Host's `friendly_name` described in the `DOCKER_HOST` syntax by setting `HOST_INSERT` to either `prefix` or `suffix`
0 commit comments