The README's Configuration table now lists every setting upaas reads, adding UPAAS_MAINTENANCE_MODE, UPAAS_SESSION_SECRET and UPAAS_CORS_ORIGINS, and gives each row its real default and effect (#229).
docker-compose.yml now sets UPAAS_PORT to 8080 as well as PORT, so a UPAAS_PORT line in .env no longer moves upaas off the port the compose file's port mapping and healthcheck use (#230).
No code changes.
For deploying, the corrected table rows say:
UPAAS_SENTRY_DSN is read but unused; upaas reports nothing to Sentry.
UPAAS_DEBUG also sends the session cookie without the Secure flag.
Deploys need UPAAS_DATA_DIR to be absolute unless UPAAS_HOST_DATA_DIR is set.
UPAAS_PORT is also read and wins over PORT.
Model: opus-5-5
On `next`:
- The README's Configuration table now lists every setting upaas reads, adding `UPAAS_MAINTENANCE_MODE`, `UPAAS_SESSION_SECRET` and `UPAAS_CORS_ORIGINS`, and gives each row its real default and effect (https://git.eeqj.de/sneak/upaas/issues/229).
- `docker-compose.yml` now sets `UPAAS_PORT` to 8080 as well as `PORT`, so a `UPAAS_PORT` line in `.env` no longer moves upaas off the port the compose file's port mapping and healthcheck use (https://git.eeqj.de/sneak/upaas/issues/230).
No code changes.
For deploying, the corrected table rows say:
- `UPAAS_SENTRY_DSN` is read but unused; upaas reports nothing to Sentry.
- `UPAAS_DEBUG` also sends the session cookie without the `Secure` flag.
- Deploys need `UPAAS_DATA_DIR` to be absolute unless `UPAAS_HOST_DATA_DIR` is set.
- `UPAAS_PORT` is also read and wins over `PORT`.
Model: opus-5-5
The table left out UPAAS_MAINTENANCE_MODE, UPAAS_SESSION_SECRET and
UPAAS_CORS_ORIGINS, and several rows gave the wrong default or effect.
Each row now matches internal/config/config.go and the code that uses
the value: UPAAS_PORT is also read and wins over PORT, UPAAS_DATA_DIR
must be absolute for deploys unless UPAAS_HOST_DATA_DIR is set,
UPAAS_HOST_DATA_DIR falls back to UPAAS_DATA_DIR and must be absolute
when set, UPAAS_DEBUG also drops the session cookie's Secure flag,
UPAAS_SENTRY_DSN is not used, and /metrics exists only when
UPAAS_METRICS_USERNAME is set. A sentence under the table names the
standard Docker client variables. TODO.md records the step.
Model: opus-5-5
Co-authored-by: clawbot <sneak+clawbot@sneak.cloud>
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
clawbot
changed title from Merge next into main: every setting upaas reads in the README to Merge next into main: every setting upaas reads in the README, UPAAS_PORT in the Compose file2026-09-29 05:27:01 +02:00
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
On
next:UPAAS_MAINTENANCE_MODE,UPAAS_SESSION_SECRETandUPAAS_CORS_ORIGINS, and gives each row its real default and effect (#229).docker-compose.ymlnow setsUPAAS_PORTto 8080 as well asPORT, so aUPAAS_PORTline in.envno longer moves upaas off the port the compose file's port mapping and healthcheck use (#230).No code changes.
For deploying, the corrected table rows say:
UPAAS_SENTRY_DSNis read but unused; upaas reports nothing to Sentry.UPAAS_DEBUGalso sends the session cookie without theSecureflag.UPAAS_DATA_DIRto be absolute unlessUPAAS_HOST_DATA_DIRis set.UPAAS_PORTis also read and wins overPORT.Model: opus-5-5
Merge next into main: every setting upaas reads in the READMEto Merge next into main: every setting upaas reads in the README, UPAAS_PORT in the Compose fileView command line instructions
Checkout
From your project repository, check out a new branch and test the changes.