stroblmeandClaude Opus 5
73eeec29b1
One process owns this database — the image has run a single uvicorn worker for that reason since the four-engines bug — so a file beside the flows is the honest shape for it, and it is what lets `fluksio serve` need no infrastructure at all. Live values, node execution and the work queue never came here anyway; what does is a rollup a minute at a time, a row per cascade and the run history, and WAL keeps the readers going while that one writer works. DATA_DIR is now the one setting that moves everything an installation keeps; the rest derive from it and the images still spell theirs out. The schema is prepared in-process at startup, so the prestart service is gone, and the ten Postgres-only revisions collapse into one portable baseline. Three things only worked because psycopg was casting for us: a token's subject arriving as a string where the column is a UUID, `greatest`, and `date_bin`. The timestamps needed a column type of their own — SQLite stores no offset, and a naive datetime read back either raises against an aware `now` or serialises as local time. Postgres stays in the stack only for Umami, behind the analytics profile. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
65 lines
2.4 KiB
YAML
65 lines
2.4 KiB
YAML
name: Compose Smoke Test
|
|
|
|
# Lives in this repository rather than the workspace root: the stack it starts
|
|
# is entirely app-local (docker/compose*.yml + .env.example). A root workflow
|
|
# would additionally need a token to check out the private submodules and would
|
|
# have to run scripts/setup.sh to generate secrets, for the same coverage.
|
|
on:
|
|
push:
|
|
branches:
|
|
- main
|
|
paths:
|
|
- backend/**
|
|
- frontend/**
|
|
- docker/compose*.yml
|
|
- .env.example
|
|
- .gitea/workflows/test-compose.yml
|
|
pull_request:
|
|
types:
|
|
- opened
|
|
- synchronize
|
|
paths:
|
|
- backend/**
|
|
- frontend/**
|
|
- docker/compose*.yml
|
|
- .env.example
|
|
- .gitea/workflows/test-compose.yml
|
|
|
|
env:
|
|
# compose.ci.yml drops the fixed container_names and host ports so this job
|
|
# can share a runner host with the Playwright shards.
|
|
COMPOSE_FILE: docker/compose.yml:docker/compose.dev.yml:docker/compose.ci.yml
|
|
# Own project name so this job's `down -v` cannot reach another stack.
|
|
COMPOSE_PROJECT_NAME: fluksio-app-ci-compose
|
|
|
|
jobs:
|
|
test-compose:
|
|
runs-on: ubuntu-latest
|
|
timeout-minutes: 30
|
|
steps:
|
|
- name: Checkout
|
|
uses: actions/checkout@v4
|
|
- name: Write .env
|
|
run: cp .env.example .env
|
|
# The Playwright job runs the SPA off a Vite server inside its own
|
|
# container, so the nginx image is only ever built there. This job is what
|
|
# covers it — the SPA fallback in frontend/nginx.conf is the part that
|
|
# breaks silently.
|
|
- run: docker compose build backend frontend
|
|
- run: docker compose down -v --remove-orphans
|
|
# Redis comes along as a depends_on; --wait blocks on the backend
|
|
# healthcheck in docker/compose.yml, which is also what proves the
|
|
# schema was created before anything served a request.
|
|
- run: docker compose up -d --wait backend frontend
|
|
# Nothing is published on the host (compose.ci.yml), so the checks run
|
|
# from inside the backend container against the project network.
|
|
- name: Backend is up
|
|
run: docker compose exec -T backend curl -f http://localhost:8000/api/v1/utils/health-check/
|
|
- name: Frontend is up
|
|
run: docker compose exec -T backend curl -f http://frontend/
|
|
- name: An authenticated route serves the SPA shell
|
|
run: docker compose exec -T backend curl -f http://frontend/flows
|
|
- name: Tear down
|
|
if: always()
|
|
run: docker compose down -v --remove-orphans
|