df409f88b3
All checks were successful
PR build (required check) / changes (pull_request) Successful in 6s
secrets-guard / encrypted (pull_request) Successful in 4s
shell-lint / shellcheck (pull_request) Successful in 6s
PR build (required check) / validate-observability (pull_request) Successful in 20s
PR build (required check) / build-frontend (pull_request) Successful in 37s
PR build (required check) / build-backend (pull_request) Successful in 51s
PR build (required check) / gate (pull_request) Successful in 1s
Repos moved to the Jinemi org; the container packages did not follow, since
Forgejo does not transfer packages with a repo. The deploy path still resolved
`emi/thermograph/*` — a user_redirect to admin_emi — while build-push.yml
derives its push path from ${github.repository}, now jinemi/thermograph. The
next backend or frontend build would have published somewhere no deploy looks.
Point the image paths at jinemi/thermograph/* (lowercase: OCI references admit
no uppercase, which is why build-push.yml already pipes through tr), the clone
URLs at Jinemi/thermograph, and the registry logins at admin_emi — the account
that actually owns the tokens, rather than the redirect.
The live tags and both ci-runner tags were copied into the Jinemi namespace
first, so the switch has something to pull. thermograph-infra,
thermograph-observability and the retired */app packages stay under admin_emi;
they did not move.
45 lines
2.2 KiB
YAML
45 lines
2.2 KiB
YAML
# Boot-smoke harness: run the backend's OWN image against a throwaway TimescaleDB and
|
|
# assert it actually boots + serves its contract (build alone doesn't prove boot). Used
|
|
# by scripts/smoke.sh; not a deploy file. DB data is tmpfs (ephemeral) — no volume, no
|
|
# residue. See Makefile `smoke` and README.
|
|
services:
|
|
db:
|
|
image: timescale/timescaledb:${TIMESCALEDB_TAG:-latest-pg18}
|
|
environment:
|
|
POSTGRES_USER: thermograph
|
|
POSTGRES_PASSWORD: ${POSTGRES_PASSWORD:-smoke}
|
|
POSTGRES_DB: thermograph
|
|
tmpfs:
|
|
# pg18 images place PGDATA in a major-version subdir under the mount, so mount at
|
|
# /var/lib/postgresql (matches the infra compose), not /var/lib/postgresql/data.
|
|
- /var/lib/postgresql
|
|
healthcheck:
|
|
test: ["CMD-SHELL", "pg_isready -U thermograph -d thermograph"]
|
|
interval: 3s
|
|
timeout: 5s
|
|
retries: 20
|
|
|
|
backend:
|
|
# Defaults to a locally-built `:local` image (scripts/smoke.sh builds it). In CI,
|
|
# set BACKEND_IMAGE_TAG=sha-<12hex> to smoke the exact published image.
|
|
# The path must match what build-push.yml publishes -- jinemi/thermograph/backend.
|
|
# It read admin_emi/thermograph-backend/app (the retired split-era path) until this
|
|
# was corrected; harmless for the default `:local` build, wrong the moment
|
|
# BACKEND_IMAGE_TAG names a real published tag.
|
|
image: ${REGISTRY_HOST:-git.thermograph.org}/${BACKEND_IMAGE_PATH:-jinemi/thermograph/backend}:${BACKEND_IMAGE_TAG:-local}
|
|
depends_on:
|
|
db:
|
|
condition: service_healthy
|
|
environment:
|
|
THERMOGRAPH_DATABASE_URL: postgresql+asyncpg://thermograph:${POSTGRES_PASSWORD:-smoke}@db:5432/thermograph
|
|
# Required at import (web/app.py). The smoke never exercises a proxied page, so an
|
|
# unreachable placeholder is fine — it only hits /healthz and {BASE}/api/version.
|
|
THERMOGRAPH_FRONTEND_BASE_INTERNAL: http://127.0.0.1:1
|
|
THERMOGRAPH_BASE: "/"
|
|
THERMOGRAPH_ENABLE_NOTIFIER: "0"
|
|
THERMOGRAPH_ENABLE_HEARTBEAT: "0"
|
|
PORT: "8137"
|
|
WORKERS: "1"
|
|
ports:
|
|
# Host port defaults to 18137 to avoid colliding with a running dev server on 8137.
|
|
- "127.0.0.1:${SMOKE_HOST_PORT:-18137}:8137"
|