sneak/upaas
1
0
Fork 1
Code Issues 4 Pull Requests 1 Actions Packages Projects Releases 1 Wiki Activity

docker-compose.yml for deploying upaas (urgent) #223

New Issue
Open
opened 2026-09-28 11:24:33 +02:00 by clawbot · 2 comments
clawbot commented 2026-09-28 11:24:33 +02:00
Collaborator
Copy Link
Copy Source

sneak's order, 09:2x UTC 2026-09-28, verbatim:

write a docker-compose for upaas asap and get it on 'main' or 'prod' or whatever we're using because i'm going to deploy it in prod now

Urgent: he is deploying upaas on fsn1app1 now (issue 181). He merged the milestone, PR 207, into main at 09:20 UTC, and next was deleted with it. next has been recreated from main (97a17e56a7) as the base for this PR.

Definition of done:

  • A docker-compose.yml at the repo root runs upaas as the README describes: the image built from this repo's Dockerfile, the Docker socket and data mounts upaas needs to deploy apps, settings from an .env file, and restart: unless-stopped.
  • It follows the rehearsal's advice (comment 102392): the upaas port is published on 127.0.0.1 only, for the TLS proxy in front, and UPAAS_PLAINTEXT_HTTP is left unset.
  • It works: docker compose up -d from a fresh clone brings upaas up healthy, and the web UI answers on the published port. The worker checks this and then removes everything it started.
  • The README gets a short "Deploying with Docker Compose" section.
  • make check is green; the PR to next passes an independent review and is merged. The next to main PR is open, mergeable, and assigned to sneak.
  • As soon as the review passes, sneak gets the file's raw URL in chat, so he can deploy before the merge to main.

Model: opus-5-5

sneak's order, 09:2x UTC 2026-09-28, verbatim: > write a docker-compose for upaas asap and get it on 'main' or 'prod' or whatever we're using because i'm going to deploy it in prod now **Urgent:** he is deploying upaas on fsn1app1 now ([issue 181](https://git.eeqj.de/sneak/upaas/issues/181)). He merged the milestone, [PR 207](https://git.eeqj.de/sneak/upaas/pulls/207), into `main` at 09:20 UTC, and `next` was deleted with it. `next` has been recreated from `main` (`97a17e56a7`) as the base for this PR. Definition of done: - A `docker-compose.yml` at the repo root runs upaas as the README describes: the image built from this repo's `Dockerfile`, the Docker socket and data mounts upaas needs to deploy apps, settings from an `.env` file, and `restart: unless-stopped`. - It follows the rehearsal's advice ([comment 102392](https://git.eeqj.de/sneak/upaas/issues/181#issuecomment-102392)): the upaas port is published on `127.0.0.1` only, for the TLS proxy in front, and `UPAAS_PLAINTEXT_HTTP` is left unset. - It works: `docker compose up -d` from a fresh clone brings upaas up healthy, and the web UI answers on the published port. The worker checks this and then removes everything it started. - The README gets a short "Deploying with Docker Compose" section. - `make check` is green; the PR to `next` passes an independent review and is merged. The `next` to `main` PR is open, mergeable, and assigned to sneak. - As soon as the review passes, sneak gets the file's raw URL in chat, so he can deploy before the merge to `main`. Model: opus-5-5
clawbot commented 2026-09-28 11:25:37 +02:00
Author
Collaborator
Copy Link
Copy Source

Plan: one PR to next, done by one worker, then an independent review.

  • docker-compose.yml at the repo root: build: ., restart: unless-stopped, the Docker socket mounted, ${HOST_DATA_DIR} (an absolute host path) mounted at /var/lib/upaas and passed as UPAAS_HOST_DATA_DIR, settings read from .env, port published as 127.0.0.1:8080:8080, UPAAS_PLAINTEXT_HTTP not set, and a healthcheck against /health so docker compose ps shows the container as healthy.
  • README: the existing Docker Compose example (which serves plain HTTP on every interface) becomes a short "Deploying with Docker Compose" section that points at the file and lists the .env settings, so the two can't drift apart.
  • Proof: docker compose up -d from a fresh clone under a unique project name, the container becomes healthy, and the UI answers on 127.0.0.1. Then the worker removes every container, volume, network and image that run created, and nothing else.
  • As soon as the review passes, the raw URL of the file on the PR branch is posted here so the deploy doesn't have to wait for the merge.

Model: opus-5-5

Plan: one PR to `next`, done by one worker, then an independent review. - `docker-compose.yml` at the repo root: `build: .`, `restart: unless-stopped`, the Docker socket mounted, `${HOST_DATA_DIR}` (an absolute host path) mounted at `/var/lib/upaas` and passed as `UPAAS_HOST_DATA_DIR`, settings read from `.env`, port published as `127.0.0.1:8080:8080`, `UPAAS_PLAINTEXT_HTTP` not set, and a healthcheck against `/health` so `docker compose ps` shows the container as healthy. - README: the existing Docker Compose example (which serves plain HTTP on every interface) becomes a short "Deploying with Docker Compose" section that points at the file and lists the `.env` settings, so the two can't drift apart. - Proof: `docker compose up -d` from a fresh clone under a unique project name, the container becomes healthy, and the UI answers on `127.0.0.1`. Then the worker removes every container, volume, network and image that run created, and nothing else. - As soon as the review passes, the raw URL of the file on the PR branch is posted here so the deploy doesn't have to wait for the merge. Model: opus-5-5
clawbot commented 2026-09-28 12:11:27 +02:00
Author
Collaborator
Copy Link
Copy Source

The review of #225 has passed. The file:

https://git.eeqj.de/sneak/upaas/raw/branch/docker-compose/docker-compose.yml

It builds the image from the repo, so run it from a clone, not from the file alone:

git clone -b docker-compose https://git.eeqj.de/sneak/upaas.git && cd upaas
echo HOST_DATA_DIR=/srv/upaas/data > .env
docker compose up -d

HOST_DATA_DIR must be an absolute path. upaas is published on 127.0.0.1:8080 for the TLS proxy. Settings in .env use the UPAAS_ prefix (UPAAS_SENTRY_DSN and so on).

Model: opus-5-5

The review of https://git.eeqj.de/sneak/upaas/pulls/225 has passed. The file: https://git.eeqj.de/sneak/upaas/raw/branch/docker-compose/docker-compose.yml It builds the image from the repo, so run it from a clone, not from the file alone: ```sh git clone -b docker-compose https://git.eeqj.de/sneak/upaas.git && cd upaas echo HOST_DATA_DIR=/srv/upaas/data > .env docker compose up -d ``` `HOST_DATA_DIR` must be an absolute path. upaas is published on `127.0.0.1:8080` for the TLS proxy. Settings in `.env` use the `UPAAS_` prefix (`UPAAS_SENTRY_DSN` and so on). Model: opus-5-5
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
Something is not working
 duplicate
This issue or pull request already exists
 enhancement
New feature
 help wanted
Need some help
 invalid
Something is wrong
 merge-ready
All checks pass, reviewed, rebased, ready for merge
 needs-checks
make check does not pass cleanly
 needs-rebase
PR has merge conflicts or is behind main
 needs-review
Code review not yet done
 needs-rework
Code review found issues to fix
 notplanned
question
More information is needed
 wontfix
This won't be fixed
No labels
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Assignees
Clear assignees
clawbot sneak (Jeffrey Paul)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: sneak/upaas#223