docs(readme): production in the fleet deploys from infra/komodo, make deploy stays for a checkout deployed by hand

fix(gitignore): anchor /t/ to the root, it hid routes like (internal)/t/
2026-10-08 04:40:25 +00:00 · 2026-10-08 04:37:26 +00:00
2 changed files with 3 additions and 1 deletions
@@ -15,4 +15,4 @@ node_modules/
 /build/
 {% endif %}
 # Local playground
-t/
+/t/
@@ -13,4 +13,6 @@ make recreate

 To deploy, `git pull && make deploy`. It runs `make pre-deploy` in every part, which builds images only when their inputs changed and applies migrations, then `docker compose up -d`, then `make post-deploy`, which restarts the services whose mounted code changed. A deploy system with its own `up` step calls the two hooks around it. What was built and started is remembered as `refs/deploy/*` in the clone.

+In the fleet, production is deployed from `infra/komodo` instead (git mode of Komodo, see `docs/architecture.md` there): Komodo clones this repo, and a layer plus `deploy.sh` in the stack's directory tag images by the hash of what they bake in, write `.env` from sops and run migrations before the code. The repo only has to stay a plain recipe: images built from `build:` in compose, migrations as the `migrator` service when there is a database, `caddy/site.caddy`. `make deploy` and `refs/deploy/*` are for a checkout deployed by hand.
+
 `make fmt`, `make check` and `make build` run in every part. Part-specific targets live in the part's own Makefile: `make -C {{ parts[0] }} ...`.
Author	SHA1	Message	Date
hh	940a599515	docs(readme): production in the fleet deploys from infra/komodo, make deploy stays for a checkout deployed by hand	2026-10-08 04:40:25 +00:00
hh	e38ca1bf26	fix(gitignore): anchor /t/ to the root, it hid routes like (internal)/t/	2026-10-08 04:37:26 +00:00