4dcd6775c4
All checks were successful
secrets-guard / encrypted (pull_request) Successful in 5s
shell-lint / shellcheck (pull_request) Successful in 7s
PR build (required check) / changes (pull_request) Successful in 19s
PR build (required check) / build-backend (pull_request) Has been skipped
PR build (required check) / build-frontend (pull_request) Has been skipped
PR build (required check) / validate-observability (pull_request) Has been skipped
PR build (required check) / gate (pull_request) Successful in 1s
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
secrets-guard / encrypted (push) Successful in 6s
Sync infra to hosts / sync-dev (push) Successful in 12s
shell-lint / shellcheck (push) Successful in 8s
A fresh checkout had no working path to the stack locally. Neither compose file carries a `build:` for backend or frontend -- each ships as its own registry image -- so with no image present `make dev-up` fell through to pulling the `:local` tag, which nothing publishes, and failed with 403 against a registry a laptop has no login for. `install` builds both images from backend/Dockerfile and frontend/Dockerfile under exactly the tag the compose files default to; `up` verifies they exist and says what to run instead of retrying the pull. Image names are read back from `docker compose config --images` rather than restated here, so an org rename cannot leave this file building a tag nothing runs. infra's dev-up/dev-down now set COMPOSE_PROJECT_NAME=thermograph-dev, which matches deploy/deploy-dev.sh and what the root CLAUDE.md already described; a local run previously landed in the prod-shaped `thermograph` project. Drop dev-up's `--build`, a no-op since the Dockerfiles moved out of infra, and correct the comment claiming a 0.0.0.0 default -- the overlay has published on loopback since dev moved to a public VPS. |
||
|---|---|---|
| .. | ||
| onboarding | ||