On next: docker-compose.yml for deploying upaas (#223), plus a README section "Deploying with Docker Compose".
To deploy:
Put HOST_DATA_DIR=/absolute/host/path in .env next to the file, then run docker compose up -d. Other settings go in the same .env.
upaas is published on 127.0.0.1:8080 only, for the TLS proxy in front. UPAAS_PLAINTEXT_HTTP stays unset.
The file sets PORT and UPAAS_DATA_DIR itself, so setting either in .env has no effect.
What changes for existing installs: upaas now refuses to start when UPAAS_HOST_DATA_DIR is set to a relative path. Before, it started and failed at the first app build.
Settings are read with the UPAAS_ prefix (UPAAS_DEBUG, UPAAS_SENTRY_DSN, UPAAS_METRICS_USERNAME/UPAAS_METRICS_PASSWORD). The README's Configuration table leaves the prefix off for those four, which #224 tracks.
Model: opus-5-5
On `next`: `docker-compose.yml` for deploying upaas (https://git.eeqj.de/sneak/upaas/issues/223), plus a README section "Deploying with Docker Compose".
To deploy:
- Put `HOST_DATA_DIR=/absolute/host/path` in `.env` next to the file, then run `docker compose up -d`. Other settings go in the same `.env`.
- upaas is published on `127.0.0.1:8080` only, for the TLS proxy in front. `UPAAS_PLAINTEXT_HTTP` stays unset.
- The file sets `PORT` and `UPAAS_DATA_DIR` itself, so setting either in `.env` has no effect.
What changes for existing installs: upaas now refuses to start when `UPAAS_HOST_DATA_DIR` is set to a relative path. Before, it started and failed at the first app build.
Settings are read with the `UPAAS_` prefix (`UPAAS_DEBUG`, `UPAAS_SENTRY_DSN`, `UPAAS_METRICS_USERNAME`/`UPAAS_METRICS_PASSWORD`). The README's Configuration table leaves the prefix off for those four, which https://git.eeqj.de/sneak/upaas/issues/224 tracks.
Model: opus-5-5
The compose file builds the image from this repo, mounts the Docker
socket and HOST_DATA_DIR (passed to upaas as UPAAS_HOST_DATA_DIR),
reads settings from .env, and restarts unless stopped. The port is
published on 127.0.0.1 only, for a TLS-terminating proxy in front.
PORT and UPAAS_DATA_DIR are pinned so .env cannot move upaas off the
port mapping, the healthcheck (busybox wget) or the data mount.
upaas now refuses to start when UPAAS_HOST_DATA_DIR is set to a
relative path; when unset it still falls back to the data directory.
The README's plain-HTTP Compose example becomes a short deploy section
that points at the file. .env is added to .dockerignore.
Model: opus-5-5
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:docker-compose.ymlfor deploying upaas (#223), plus a README section "Deploying with Docker Compose".To deploy:
HOST_DATA_DIR=/absolute/host/pathin.envnext to the file, then rundocker compose up -d. Other settings go in the same.env.127.0.0.1:8080only, for the TLS proxy in front.UPAAS_PLAINTEXT_HTTPstays unset.PORTandUPAAS_DATA_DIRitself, so setting either in.envhas no effect.What changes for existing installs: upaas now refuses to start when
UPAAS_HOST_DATA_DIRis set to a relative path. Before, it started and failed at the first app build.Settings are read with the
UPAAS_prefix (UPAAS_DEBUG,UPAAS_SENTRY_DSN,UPAAS_METRICS_USERNAME/UPAAS_METRICS_PASSWORD). The README's Configuration table leaves the prefix off for those four, which #224 tracks.Model: opus-5-5