Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Describe "exposed_port" Config for Healthcheck #23

Merged
merged 3 commits into from
Sep 18, 2023
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 11 additions & 0 deletions _docs/configuration.md
Original file line number Diff line number Diff line change
Expand Up @@ -693,6 +693,17 @@ The HTTP health checks assume that the `curl` command is available inside the co

When starting container healthcheck by default will only show last 50 lines. That might be not enough when something goes wrong - so you can add `log_lines` params and specify larger number if required.

## Using a custom port for the healthcheck with multiple apps

Healthcheck is binding containers port to server's port. When running multiple applications on the same server and deploying them in parallel you should specify different port for each application.

```yaml
healthcheck:
exposed_port: 4000 # 3999 is the default one
```

This allows you to run multiple applications on the same server sharing the same Traefik instance and port

## Using rolling deployments

When deploying to large numbers of hosts, you might prefer not to restart your services on every host at the same time.
Expand Down