Thermograph monorepo: graded-climate API + SSR frontend + infra, domain-specific containerized deploys
Find a file
admin_emi 1afe6fbaac
All checks were successful
secrets-guard / encrypted (push) Successful in 7s
shell-lint / shellcheck (push) Successful in 9s
Build + push images (Forgejo registry) / build-push (backend) (push) Successful in 24s
Build + push images (Forgejo registry) / build-push (frontend) (push) Successful in 1m15s
Deploy / deploy (backend) (push) Successful in 1m30s
Deploy / deploy (frontend) (push) Successful in 1m44s
Merge pull request 'promote: main → release (jinemi registry namespace, Caddy trusted_proxies, CI login fix)' (#159) from main into release
2026-08-01 19:38:48 +00:00
.claude BRANCHING: the escape hatch, now that apply_to_admins binds the owner too 2026-07-26 15:05:26 -07:00
.forgejo/workflows build-push: drop the empty ${{ }} that silenced the registry login 2026-08-01 11:17:48 -07:00
backend docs: correct file references and the dev reachability claim 2026-08-01 11:49:28 -07:00
docs/onboarding registry: move image and repo references to the Jinemi namespace 2026-08-01 09:25:02 -07:00
frontend registry: move image and repo references to the Jinemi namespace 2026-08-01 09:25:02 -07:00
infra Merge dev into feat/forgejo-runners (dev moved while #157 was open) 2026-08-01 11:52:12 -07:00
observability docs: correct file references and the dev reachability claim 2026-08-01 11:49:28 -07:00
.gitignore gitignore: ignore .claude/settings.local.json 2026-08-01 09:16:06 -07:00
CLAUDE.md docs: correct file references and the dev reachability claim 2026-08-01 11:49:28 -07:00
CUTOVER-NOTES.md registry: move image and repo references to the Jinemi namespace 2026-08-01 09:25:02 -07:00
README.md registry: move image and repo references to the Jinemi namespace 2026-08-01 09:25:02 -07:00

thermograph

The Thermograph monorepo — the split repos reunified (2026-07-22) with full history via subtree merges, while keeping everything the split was actually for: per-domain images, per-domain deploys, and an async FE/BE contract.

Domains

Dir What CI
backend/ FastAPI graded-climate API, accounts, notifications (Discord bot, push, mail), data pipeline build-push → image jinemi/thermograph/backend; deploy
frontend/ Public client: static JS/CSS + SSR pages same build-push / deploy workflows, matrixed by domain; image jinemi/thermograph/frontend
infra/ Compose (dev, on vps1) + two Swarm stacks co-resident on vps2 (beta, prod), deploy scripts, terraform, SOPS secrets vault, ops cron infra-sync (host checkout + secrets render), secrets-guard, ops-cron
observability/ Loki + Grafana + Alloy stack observability-validate

thermograph-docs deliberately stays its own repo (ADRs + runbooks, no build artifacts, different change cadence).

New here?

docs/onboarding/ is the developer onboarding path: orientation, verified local-setup recipes, a per-domain deep dive, the cross-service contracts that break silently, the release flow, and a list of which docs in this repo are currently stale.

How CI stays decoupled

Every workflow in .forgejo/workflows/ is path-filtered to its domain: a push touching only frontend/** builds/deploys nothing else. Images stay separate (jinemi/thermograph/backend, jinemi/thermograph/frontend, each tagged sha-<12hex>), deploys stay per-service (infra/deploy/deploy.sh SERVICE=backend|frontend|all), and the API version contract (GET /api/version, PAYLOAD_VER) still lets FE and BE ship out of lockstep. The one intentionally coupled piece is pr-build.yml: a single always-running gate required check that builds only the domains a PR touches (a path-filtered required check would deadlock auto-merge).

Branch model (unchanged from the split era): PRs → dev, main → beta, release → prod. Infra isn't environment-staged the same way app images are: beta's and prod's checkouts (both on vps2) track main; dev's checkout (on vps1) tracks dev itself, since it's the one environment that isn't a rehearsal for something downstream.

Before pointing anything live at this repo, read CUTOVER-NOTES.md.