nexus/WifiPoolToMQTT
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages 1 Wiki Activity Actions

Make the published health port configurable #8

Merged
nexus merged 1 commit from ci/configurable-health-port into main 2026-07-23 15:15:48 +02:00
Conversation 0 Commits 1 Files changed 3 +15 -3
nexus commented 2026-07-23 14:44:22 +02:00
Owner
Copy link

Deploying on a NAS failed with:

failed to bind host port 0.0.0.0:8080/tcp: address already in use

Nothing wrong with the tool — something else on that host already listens on
8080. It is a popular port, so this is the most likely first stumble for anyone
following the README, and it deserves an answer in the file rather than in a
chat.

The compose file now publishes ${HEALTH_PORT:-8080}:8080. Only the host side
moves; the container keeps listening on 8080, so HEALTH_ADDR and the
healthcheck are untouched. HEALTH_PORT is documented in .env.example, and
the README names the error and the two ways out — set the variable, or drop the
ports section entirely, since the healthcheck runs inside the container and
needs no published port.

Interpolation verified with podman-compose 1.5.0: the default applies without
an .env, and HEALTH_PORT=18080 in .env comes through.

Deploying on a NAS failed with: failed to bind host port 0.0.0.0:8080/tcp: address already in use Nothing wrong with the tool — something else on that host already listens on 8080. It is a popular port, so this is the most likely first stumble for anyone following the README, and it deserves an answer in the file rather than in a chat. The compose file now publishes `${HEALTH_PORT:-8080}:8080`. Only the host side moves; the container keeps listening on 8080, so `HEALTH_ADDR` and the healthcheck are untouched. `HEALTH_PORT` is documented in `.env.example`, and the README names the error and the two ways out — set the variable, or drop the `ports` section entirely, since the healthcheck runs inside the container and needs no published port. Interpolation verified with podman-compose 1.5.0: the default applies without an `.env`, and `HEALTH_PORT=18080` in `.env` comes through.
Make the published health port configurable
All checks were successful
CI / image (pull_request) Successful in 56s
Details
CI / test (pull_request) Successful in 3m19s
Details
CI / test (push) Successful in 3m1s
Details
CI / publish-commit-tag (pull_request) Has been skipped
Details
CI / publish-commit-tag (push) Has been skipped
Details
CI / image (push) Successful in 52s
Details
CI / publish-version-tag (pull_request) Has been skipped
Details
CI / publish-version-tag (push) Has been skipped
Details
190bf56c9e 
Deploying on a NAS failed with 'failed to bind host port 0.0.0.0:8080/tcp:
address already in use'. 8080 is a popular port and colliding with something
already on the host is the most likely first stumble, so the compose file now
takes the host side from HEALTH_PORT and the README says what to do about it.

Only the host side moves; the container keeps listening on 8080, so
HEALTH_ADDR and the healthcheck are unaffected.
nexus merged commit dce81c6fde into main 2026-07-23 15:15:48 +02:00
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels
No items
No labels
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
nexus/WifiPoolToMQTT!8
No description provided.