53e2eb7c84
All checks were successful
Sync infra to hosts / sync-beta (push) Has been skipped
Sync infra to hosts / sync-prod (push) Has been skipped
Sync infra to hosts / sync-centralis (push) Has been skipped
Sync infra to hosts / sync-dev (push) Successful in 9s
secrets-guard / encrypted (push) Successful in 5s
Validate observability stack / validate (push) Successful in 12s
shell-lint / shellcheck (push) Successful in 8s
Build + push images (Forgejo registry) / build-push (frontend) (push) Successful in 26s
Build + push images (Forgejo registry) / build-push (backend) (push) Successful in 1m10s
Deploy / deploy (backend) (push) Successful in 1m41s
Deploy / deploy (frontend) (push) Successful in 1m48s
secrets-guard / encrypted (pull_request) Successful in 8s
shell-lint / shellcheck (pull_request) Successful in 9s
PR build (required check) / changes (pull_request) Successful in 20s
PR build (required check) / validate-observability (pull_request) Successful in 15s
PR build (required check) / build-frontend (pull_request) Successful in 17s
PR build (required check) / build-backend (pull_request) Successful in 2m26s
PR build (required check) / gate (pull_request) Successful in 1s
Completes the Forgejo domain migration. ROOT_URL moved to dev.jinemi.com earlier; the registry half was deliberately deferred. Every image name, REGISTRY_HOST default, runner label and --add-host pin now names dev.jinemi.com, so the registry host and the bearer-token realm agree again. Both names address the same Forgejo, so no image needs re-pushing and a rollback to a tag pushed under the old prefix still resolves. git.thermograph.org therefore stays served off the same Caddy site block -- one block, so the /v2/* mesh-only matcher keeps covering both names -- for pre-migration tags and for runners holding it as their registered instance URL. Mesh clients now pin both names in /etc/hosts: the new one as registry host and token realm, the old one for pre-migration tags. runner-vps2/config.yaml carries both --add-host entries for the same reason. Also renames Centralis' endpoint to mcp.jinemi.com in the two places this repo names it; Centralis itself is provisioned outside this repo. Host-side steps this cannot do (documented in deploy/forgejo/README.md, "Host-side steps"): the Forgejo Actions variable REGISTRY_HOST, docker login against the new host, and the /etc/hosts pins.
64 lines
3 KiB
Text
64 lines
3 KiB
Text
# Local docker-compose overrides. Copy to .env (gitignored) for `docker compose
|
|
# up` / `make up` on a laptop: cp .env.example .env
|
|
#
|
|
# Compose auto-reads a repo-root .env for ${VAR} interpolation in
|
|
# docker-compose.yml. On the fleet (dev/beta/prod), these values live in each
|
|
# environment's own rendered env file instead (/etc/thermograph.env,
|
|
# /etc/thermograph-beta.env — see deploy/secrets/README.md), so this file is
|
|
# only for a local, unmanaged run.
|
|
|
|
# Database password. Compose uses it to initialize the postgres container AND to
|
|
# build the app's THERMOGRAPH_DATABASE_URL. Change it before first `up`.
|
|
POSTGRES_PASSWORD=change-me
|
|
|
|
# OPTIONAL. Shared secret between the daemon service (Discord gateway + job
|
|
# timers) and the backend's /internal/* routes.
|
|
#
|
|
# Leave it empty and both ends DERIVE the same token from THERMOGRAPH_AUTH_SECRET
|
|
# (HMAC-SHA256 under a fixed label), which every environment already provisions —
|
|
# so the daemon needs no new vault entry and no operator step. Set it only to
|
|
# override that, e.g. to rotate this surface independently of the auth secret:
|
|
# openssl rand -hex 32
|
|
#
|
|
# With neither this nor THERMOGRAPH_AUTH_SECRET set, both ends fail closed: the
|
|
# backend disables the internal routes and the daemon refuses to start. Never
|
|
# routed publicly — Caddy only forwards /api/*, /digest and
|
|
# /discord/interactions to the backend.
|
|
THERMOGRAPH_INTERNAL_TOKEN=
|
|
|
|
# --- Everything below is optional -- docker-compose.yml already defaults each
|
|
# --- of these, so a plain `make up` works with none of it set. Uncomment to
|
|
# --- override.
|
|
|
|
# TimescaleDB image tag. Defaults to the floating latest-pg18 tag. Pin it to an
|
|
# exact minor (e.g. 2.17.2-pg18) before any host of this stack could ever
|
|
# replicate with another -- see docker-compose.yml's db service comment.
|
|
# TIMESCALEDB_TAG=latest-pg18
|
|
|
|
# Postgres sizing. Only meaningful for an environment that runs its OWN db
|
|
# service — dev's compose stack (this file) and prod's Swarm stack, which
|
|
# sizes the ONE shared TimescaleDB instance on vps2 (see
|
|
# deploy/secrets/prod.yaml, currently DB_MEMORY=16g). Beta shares that same
|
|
# instance rather than running a second one, so a DB_MEMORY/DB_CPUS value in
|
|
# beta's own vault file no longer sizes anything — don't be misled by its
|
|
# presence there. Local/dev default to 8g / 2 CPUs.
|
|
# DB_MEMORY=8g
|
|
# DB_CPUS=2
|
|
|
|
# Backend uvicorn worker count and CPU cap. Terraform raises these on bigger
|
|
# hosts; defaults keep a plain `docker compose up` identical to before.
|
|
# WORKERS=4
|
|
# APP_CPUS=4
|
|
|
|
# Frontend CPU cap.
|
|
# FRONTEND_CPUS=2
|
|
|
|
# Registry + per-service image path/tag. Local dev normally builds each image
|
|
# in its own app repo (thermograph-backend / thermograph-frontend) tagged
|
|
# :local, which is the default here -- only set these to pull a specific
|
|
# published build instead of building locally.
|
|
# REGISTRY_HOST=dev.jinemi.com
|
|
# BACKEND_IMAGE_PATH=admin_emi/thermograph-backend/app
|
|
# BACKEND_IMAGE_TAG=local
|
|
# FRONTEND_IMAGE_PATH=admin_emi/thermograph-frontend/app
|
|
# FRONTEND_IMAGE_TAG=local
|