The health router is mounted at prefix="/api" in domaindingo's main.py, so
/health 404s. Checking it would have failed every deploy and rolled back a
perfectly good image.
Also adopts three conventions from the vault's DomainDingo Development note:
recreate a single named service (--no-deps --force-recreate), validate with
compose config --quiet before touching the running container, and write the
rollback record in the documented format and location.
- enabled_targets/names_for: one implementation of 'a host acts only on its
own targets'; --host s5 and --host s5.fisher.hu now select the same targets
- shell_value: JSON booleans reach shell consumers as true/false
- cd-status: capture before eval, so the unconfigured-host branch is reachable
- cd-deploy writes a .status record; cd-status reads it instead of grepping
the log's prose
- cd-render-hooks --list-urls replaces two inline JSON readers
The registry reserves 20000-20099 for Gitea and requires new blocks to come
from the 21500-21999 free pool, claimed only once a service is actually
listening. Also corrects the clone URL to fisher/my-cd-webhook.
Replaces the per-project deploy scripts and self-contained webhook
receivers with one manifest-driven implementation that lives outside the
application repositories and can be updated independently of them.
First targets: domaindingo test and prod on s5.
fisher