Docs: amber-api and amber-backend DO deploy on push

The deploy docs written earlier today said a push to amber-api or amber-backend
deploys nothing, from a 2026-09-13 reading of Coolify records where every deploy
of both is is_api=true. Measured against commit times, every one of those
deploys started 2 to 4 s after its commit, including two README-only pushes on
2026-09-15 that nobody deployed by hand (21:02:14 -> 21:02:18, 21:02:17 ->
21:02:20). A push reaches Coolify through its deploy API, so the record says
is_api. The hook config itself was not inspected (no Forgejo API token).

Corrected the README deploy section to say a push deploys within seconds, and
that a manual deploy is only for a push no deployment followed.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This commit is contained in:
Claude 2026-09-15 21:12:59 +02:00
parent ce9aa61bab
commit 580f43d19d

View file

@ -163,13 +163,14 @@ app `amber-backend`, uuid `eu3wk4j0zf0uczhbew0m5c9p`, serving
`pb.petruzalekr.cz` and `amber.petruzalekr.cz` on port 8090, with a persistent
volume at `/pb_data`.
**A push does not deploy it.** Coolify's git source is
`https://projects.petruzalekr.cz/richiexec/myanime-backend.git` (the old name,
redirected to this repo), branch `main`, and nothing tells Coolify about a push.
It deploys only when someone asks: the app's **Deploy** button in Coolify, or
`GET /api/v1/deploy?uuid=eu3wk4j0zf0uczhbew0m5c9p` with the Coolify API token.
Every recorded deploy of it was such a call. Push first, then deploy; a push on
its own leaves the old build serving.
**A push to `main` deploys it to production within seconds.** Coolify's git source
is `https://projects.petruzalekr.cz/richiexec/myanime-backend.git` (the old name,
redirected to this repo), branch `main`.
- Its deployment records say `is_api` rather than webhook, but every one since
2026-09-13 started 2 to 4 seconds after its commit.
- If no deployment follows a push, deploy by hand: the app's **Deploy** button in
Coolify, or `GET /api/v1/deploy?uuid=eu3wk4j0zf0uczhbew0m5c9p` with the Coolify
API token.
Migrations and hooks are baked into the image and apply when the new container
boots, so a schema or hook change reaches production only with a deploy.