From bdc5ef4f0dbf3f19e16fafb62e65cba4dbaafd94 Mon Sep 17 00:00:00 2001 From: Babissimo Date: Thu, 20 Aug 2026 17:59:01 +0100 Subject: [PATCH] docs: restore the wrong-service-name warning, corrected (86c990cfh) #212 deleted this note on the grounds that the rename resolved the trap it described. That was wrong, and the reasoning behind it was too: the failure was never that compose returns nothing. It is that `no such service` goes to stderr, so a grep over the output matches nothing and reads as a clean "no errors in the logs". That is what produced a false all-clear on production on 2026-08-14. The rename does not remove that trap, it swaps which name triggers it, and the new losing guess is `tower-finder`: the name in every saved command, older ticket and operator's memory. So the warning is worth more after the rename than before it, not less. --- ONBOARDING.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/ONBOARDING.md b/ONBOARDING.md index 161a49d9..863021c2 100644 --- a/ONBOARDING.md +++ b/ONBOARDING.md @@ -237,6 +237,10 @@ branch, open a PR, get it green, then merge. branch got no tests, no lint and no build while the lone green automated-review tick made the page read as passing. Stacked PRs opened since run the full matrix, but an older branch keeps the old workflow until it is rebased. +- **The compose service is `server`, not `tower-finder`.** Naming a service that + does not exist fails with `no such service` on *stderr*, so a `grep` over the output + matches nothing and reads as a clean "no errors in the logs". Run `docker compose ps + --services` first and trust it over a remembered name. - **A new per-environment key needs an `env-parity` entry** or CI fails. ## Where to go next