Thermograph monorepo: graded-climate API + SSR frontend + infra, domain-specific containerized deploys
Find a file
Emi Griffith ce454e0be6 deploy.sh + compose: two independent app images, per-service rolls
backend and frontend now reference their own images (BACKEND_IMAGE_PATH/TAG,
FRONTEND_IMAGE_PATH/TAG) instead of the shared emi/thermograph/app. deploy.sh
takes SERVICE=backend|frontend|all, rolls just that service with --no-deps,
persists each service's live tag in deploy/.image-tags.env so a single-service
deploy never disturbs the sibling, and fixes the old IMAGE_TAG:? guard that
made every workflow deploy hard-fail. Health-checks per service (8137/8080).

Claude-Session: https://claude.ai/code/session_01RdARHDJaYC1wSQRTYM6t3Z
2026-07-22 11:39:16 -07:00
.claude/skills/key-gaps Git-native secrets vault (SOPS + age) (#34) 2026-07-22 03:21:46 +00:00
.forgejo/workflows Git-native secrets vault (SOPS + age) (#34) 2026-07-22 03:21:46 +00:00
deploy deploy.sh + compose: two independent app images, per-service rolls 2026-07-22 11:39:16 -07:00
terraform Decouple Terraform from the app repo; add a GCP host scaffold 2026-07-21 21:46:05 -07:00
.gitignore Decouple Terraform from the app repo; add a GCP host scaffold 2026-07-21 21:46:05 -07:00
.sops.yaml Git-native secrets vault (SOPS + age) (#34) 2026-07-22 03:21:46 +00:00
ACCESS.md Decouple Terraform from the app repo; add a GCP host scaffold 2026-07-21 21:46:05 -07:00
docker-compose.openmeteo.yml Repo-split Stage 4: cut prod traffic to backend + frontend, dual-service (#14) 2026-07-21 20:01:30 +00:00
docker-compose.yml deploy.sh + compose: two independent app images, per-service rolls 2026-07-22 11:39:16 -07:00
docker-stack.yml Extract docs/ into thermograph-docs (repo-split Stage 6) (#20) 2026-07-21 21:29:14 +00:00
README.md Decouple Terraform from the app repo; add a GCP host scaffold 2026-07-21 21:46:05 -07:00

thermograph-infra

Infrastructure for Thermograph: Terraform host provisioning, the SOPS+age secrets vault, Docker Swarm/WireGuard networking, Forgejo, Caddy, and the deploy scripts that run the already-built app image on each host. Extracted from the app monorepo (emi/thermograph) — the app repo owns building and testing the app; this repo owns running it.

  • terraform/ — provisions/configures hosts (SSH-driven by default; an optional GCP-creating module is scaffolded, no live resources yet) and triggers each deploy. See terraform/README.md.
  • deploy/secrets/ — the git-native SOPS+age secrets vault (every app secret, encrypted at rest, rendered at deploy time). See deploy/secrets/README.md.
  • deploy/swarm/, deploy/forgejo/ — the 3-node WireGuard/Swarm cluster that hosts Forgejo (git + CI + registry); does not run the app itself. See ACCESS.md and the READMEs under each directory.
  • deploy/deploy.sh — pulls the pinned app image (IMAGE_TAG) and rolls the compose stack; invoked by Terraform and by the app repo's .forgejo/workflows/deploy.yml over SSH.
  • docker-compose*.yml, docker-stack.yml — how the app image runs (compose in production today; docker-stack.yml is a design record for a possible future Swarm-based app deploy, not currently live).

The app's own source, Dockerfile, and build/test CI stay in the app repo — this repo never checks out app source; hosts only pull tagged images from the registry. See ACCESS.md for host access and the Swarm/Forgejo topology, and terraform/README.md for the day-to-day plan/apply workflow.