templates/blank
2
0 Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

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

Browse Source
This commit was merged in pull request #1.
This commit is contained in:
hh committed 2026-10-08 04:40:25 +00:00
1 parent 0a3511a44b
commit ea78a12a83
1 file changed
+2
Download Patch File Download Diff File Expand all files Collapse all files
template/{{ part_dir }}/{% if layout == 'root' %}README.md{% endif %}.jinja
+2
View File
@@ -10,3 +10,5 @@ make recreate
`make env` creates `.env` and `docker-compose.override.yml` from their examples. `make recreate` starts the selected profiles, `make rebuild` builds the image first, `make logs`, `make restart` and `make down` do what they say.
To deploy, `git pull && make deploy`. It runs `make pre-deploy`, which rebuilds the image only when something in the repository changed, then `docker compose up -d`. A deploy system with its own `up` step calls `make pre-deploy` before it and `make post-deploy` after. What was built 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 and write `.env` from sops. The repo only has to stay a plain recipe: images built from `build:` in compose, `caddy/site.caddy`. `make deploy` and `refs/deploy/*` are for a checkout deployed by hand.