docs(720): name all three Komodo stacks and the label-based resolution rule (#769)
Build ErsatzTV Image / Build & test (.NET) (push) Successful in 9m24s
Build ErsatzTV Image / EF migration integrity (SQLite + MySql) (push) Successful in 7m0s
Build ErsatzTV Image / Functional E2E (curl + UI contracts) (push) Successful in 6m31s
Build ErsatzTV Image / API docs in sync (OpenAPI + endpoint index) (push) Skipped
Build ErsatzTV Image / Formatting (changed .cs conform to .editorconfig) (push) Skipped
Build ErsatzTV Image / Build & push image (amd64) (push) Successful in 6m9s
Build ErsatzTV Image / Build & test (.NET) (push) Successful in 9m24s
Build ErsatzTV Image / EF migration integrity (SQLite + MySql) (push) Successful in 7m0s
Build ErsatzTV Image / Functional E2E (curl + UI contracts) (push) Successful in 6m31s
Build ErsatzTV Image / API docs in sync (OpenAPI + endpoint index) (push) Skipped
Build ErsatzTV Image / Formatting (changed .cs conform to .editorconfig) (push) Skipped
Build ErsatzTV Image / Build & push image (amd64) (push) Successful in 6m9s
A live Komodo stack literally named `ersatztv` owns the TEST channel, not prod. `DeployStack ersatztv` succeeds, looks healthy, and promotes nothing — silent and plausible. Extends the existing callout with all three stack names and the resolution rule: identify the prod stack by the container's `com.docker.compose.project.config_files` label, not by stack name. Container labels re-verified live on jazz 2026-08-11; the verification date is scoped to what was actually re-measured, after review flagged the stamp as covering unchecked values. The server-management half (the `komodo` skill still uses the dead `media-servers` as its worked deploy target) cannot land in this repo and is tracked as server-management#743. #720's box 2 was re-scoped to that hand-off rather than ticked as though the skill were fixed. fixes #720 Co-authored-by: Timothy <timothy@noreply.gitea.tblindustries.be>
This commit was merged in pull request #769.
This commit is contained in:
@@ -114,6 +114,24 @@ commit in the range (see the `decisions.md` header) — routine lifecycle metada
|
||||
> `DeployStack media-servers` silently targets the **dead** stack. Confirm with
|
||||
> `/read ListStacks` before deploying.
|
||||
>
|
||||
> **A third stack, literally named `ersatztv`, is also live and is NOT prod**: it owns
|
||||
> `ersatztv-test`, tracks the floating `:latest` tag, and runs with `auto_update: true`. (Stack
|
||||
> name, compose project, config-file path and image tag re-confirmed from the container labels on
|
||||
> jazz 2026-08-11; the `auto_update` flags and the bumblebee `unhealthy` status are carried from
|
||||
> the earlier checks noted above, not re-measured that day.)
|
||||
> `DeployStack ersatztv` succeeds and looks healthy — it just promotes nothing to prod. Three names,
|
||||
> one target:
|
||||
>
|
||||
> | Stack name | project_name | auto_update | owns |
|
||||
> |---|---|---|---|
|
||||
> | `jazz-media` | `media-servers` | `false` | `ersatztv` (**prod**, tracks `:prod`) |
|
||||
> | `ersatztv` | `ersatztv` | `true` | `ersatztv-test` (tracks `:latest`) |
|
||||
> | `media-servers` | — | — | dead stack on bumblebee, `unhealthy` |
|
||||
>
|
||||
> Don't resolve the prod stack by name at all — resolve it by the **container's**
|
||||
> `com.docker.compose.project.config_files` label (e.g. via `docker inspect`), which points at the
|
||||
> actual compose file path and can't be confused by a same-named stack.
|
||||
>
|
||||
> **There is no Global Auto Update fallback anymore**: `jazz-media` has `auto_update: false`
|
||||
> (`poll_for_updates: true` only), so nothing promotes `:prod` on a timer — promotion is manual,
|
||||
> full stop. The old "don't cut a tag near the 03:00 run" caveat no longer applies.
|
||||
|
||||
Reference in New Issue
Block a user