Jinemi/thermograph
4
0
Fork 0
Code Issues 2 Pull requests 9 Projects Releases Packages Wiki Activity Actions
Thermograph monorepo: graded-climate API + SSR frontend + infra, domain-specific containerized deploys
70 commits 48 branches 0 tags 7.8 MiB
Python 45.6%
JavaScript 13.8%
Shell 13.6%
Go 12.8%
CSS 5.3%
Other 8.9%
Find a file
emi 9cd24387f2 Swarm stack for prod: autoscaled web tier (1-3), worker split, loopback LB (#9)
2026-07-23 04:13:12 +00:00
.claude/skills/key-gaps Docs pass after the app-repo archive; sync key-gaps skill; add CLAUDE.md (#5) 2026-07-22 23:36:21 +00:00
.forgejo/workflows Swarm stack for prod: autoscaled web tier (1-3), worker split, loopback LB (#9) 2026-07-23 04:13:12 +00:00
deploy Swarm stack for prod: autoscaled web tier (1-3), worker split, loopback LB (#9) 2026-07-23 04:13:12 +00:00
terraform terraform: per-service backend/frontend image tags (two-image contract) (#2) 2026-07-22 23:27:13 +00:00
.env.example Port orphaned infra files from monorepo (Makefile, .env.example, migrate-db, twa, DEPLOY docs) 2026-07-22 11:57:02 -07:00
.gitignore Swarm stack for prod: autoscaled web tier (1-3), worker split, loopback LB (#9) 2026-07-23 04:13:12 +00: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
CLAUDE.md Docs pass after the app-repo archive; sync key-gaps skill; add CLAUDE.md (#5) 2026-07-22 23:36:21 +00:00
DEPLOY-DEV.md Port orphaned infra files from monorepo (Makefile, .env.example, migrate-db, twa, DEPLOY docs) 2026-07-22 11:57:02 -07:00
DEPLOY.md Port orphaned infra files from monorepo (Makefile, .env.example, migrate-db, twa, DEPLOY docs) 2026-07-22 11:57:02 -07:00
docker-compose.dev.yml Add LAN-dev registry-pull artifacts: docker-compose.dev.yml + deploy-dev.sh 2026-07-22 12:20: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 Port mail provisioning from the archived app repo (+ mesh-listener knobs) (#4) 2026-07-22 23:31:33 +00:00
docker-stack.yml Extract docs/ into thermograph-docs (repo-split Stage 6) (#20) 2026-07-21 21:29:14 +00:00
Makefile Port orphaned infra files from monorepo (Makefile, .env.example, migrate-db, twa, DEPLOY docs) 2026-07-22 11:57:02 -07:00
README.md Docs pass after the app-repo archive; sync key-gaps skill; add CLAUDE.md (#5) 2026-07-22 23:36:21 +00:00

README.md

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.

Branches & how changes reach each environment

  • main — what prod and beta run: their /opt/thermograph checkouts git reset --hard origin/main at the start of every deploy (deploy/deploy.sh). A merge to main reaches those hosts on the next app deploy (or a by-hand deploy.sh run); there is no separate infra deploy trigger.
  • dev — what LAN dev runs: ~/thermograph-dev resets to it via deploy/deploy-dev.sh. Keep it fast-forwarded to main (infra changes are not environment-staged today; the branches exist so LAN dev can trail or lead when needed).
  • release — currently consumed by nothing (prod tracks main, not release). It exists to mirror the app repos' dev→main→release promotion shape if per-environment infra staging is ever wanted; until then, treat main as live-everywhere.

Note the asymmetry with the app repos: app code IS environment-staged (dev→main→release maps to LAN→beta→prod via image tags), infra is not.