Set UPAAS_PORT as well as PORT in docker-compose.yml (closes #230)
Check / check (pull_request) Skipped
Check / check (pull_request) Skipped
upaas reads UPAAS_PORT before PORT, so a UPAAS_PORT line in .env made it listen on another port than the one the compose file's port mapping and healthcheck use, and the container never became healthy. The compose file now sets both to 8080, and its comment and the README's Docker Compose section say that both are set. Model: opus-5-5
This commit is contained in:
@@ -237,10 +237,11 @@ HOST_DATA_DIR=/srv/upaas/data
|
||||
```
|
||||
|
||||
Other settings from [Configuration](#configuration) go in the same file, except
|
||||
`PORT` and `UPAAS_DATA_DIR`: the compose file sets them to 8080 and
|
||||
`/var/lib/upaas`, overriding `.env`, to match its port mapping, healthcheck and
|
||||
data directory mount. Then run `docker compose up -d` from the repo root;
|
||||
`docker compose ps` shows the container as healthy once `/health` answers.
|
||||
`PORT`, `UPAAS_PORT` and `UPAAS_DATA_DIR`: the compose file sets both port
|
||||
settings to 8080 and `UPAAS_DATA_DIR` to `/var/lib/upaas`, overriding `.env`, to
|
||||
match its port mapping, healthcheck and data directory mount. Then run
|
||||
`docker compose up -d` from the repo root; `docker compose ps` shows the
|
||||
container as healthy once `/health` answers.
|
||||
|
||||
**Important**: `HOST_DATA_DIR` **must** be an **absolute path** on the host. It
|
||||
is bind-mounted into the container and passed as `UPAAS_HOST_DATA_DIR` so that
|
||||
|
||||
Reference in New Issue
Block a user