v0.315.0: one app page with four tabs; the guide the catalog can carry; no Raspberry Pi badge
gates / gates (push) Failing after 47s

An app was six pages — details, install/settings, logs, export, the per-app backup panel and a
details card for moving data — and every "Vissza" on them went to the app LIST, so there was no way
back to the app you were looking at. It is now ONE page with four tab URLs under /apps/{slug}/,
one shared header and one set of banners.

  settings  Mukodes (Start/Restart/Stop, Stop confirms) + the cards that want something from the
            household + the install-time and optional settings. The default for an installed app,
            RENDERED at the bare URL and never redirected to.
  data      the data folders, move to another drive, the nightly copy, the 2nd-copy setting, export
  guide     tagline, screenshots, use cases, first steps, the catalog's guide, the FAQ, the docs
            link — and the WHOLE page for an app that is not installed
  logs      the log, and the only tab whose poller runs

The tabs are links, not panels: a link in an alert has to land ON a tab, and the log poller must not
run on the other three. Start/Restart/Stop left the page header, where they read as menu buttons.

The old /stacks/{name}/{deploy,logs,export,backup} GETs answer 302 — never 301, which a browser
caches beyond anyone's reach — to the tab that now holds them, query string carried through, with
name->slug resolved through the stack list rather than assumed equal. Every POST on those paths is
untouched: the backup form, the app-email toggle and the reveal endpoints keep their URLs.

A value asked AFTER the app starts is now generic (D2). The catalog marks a field `after_start: true`
and supplies its label; the ACTION is Go, in a registry keyed by slug + env var. The catalog can
never declare what runs — a declared field with no registered action renders nothing, POSTs 404 and
logs one WARN with the env var KEY, never the value. A red-proof found the second half of that guard
unpinned: deleting the "the catalog must have DECLARED this field" check left the suite green, and a
POST for an undeclared field then reached Plex and opened the setup gate.
TestAfterStart_RegistryAloneIsNotAnInvitation pins it.

New catalog block app_info.guide (sections + faq + checked_version), parsed, localised field by
field and rendered with the household's own address filled in. It renders only when checked_version
names the image tag its author clicked through. No template carries one yet.

The Pi and "csak x86" badges are gone; PiCompatible and the catalog key stay this release, or a box
on 0.314.0 would read "csak x86" on every app (R-1067).

template_id_gate.py now follows {{template}} includes, with a scope decoy proving the walk did not
become vacuous.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_0117kRTSgs3rJWUFGxyoWN6Y
This commit is contained in:
2026-10-15 18:37:50 +02:00
parent 85f65c70d8
commit e66d4669d6
120 changed files with 16239 additions and 9866 deletions
+8 -4
View File
@@ -243,7 +243,14 @@
"err.plex_claim.bad_code": "BORN AS A KEY (v0.313.0, 2026-10-15, R-1028/R-1023) — the Plex claim on the running server and the media restart's stream check; no Go literal preceded it.",
"err.plex_claim.not_claimed": "BORN AS A KEY (v0.313.0, 2026-10-15, R-1028/R-1023) — the Plex claim on the running server and the media restart's stream check; no Go literal preceded it.",
"err.plex_claim.refused": "BORN AS A KEY (v0.313.0, 2026-10-15, R-1028/R-1023) — the Plex claim on the running server and the media restart's stream check; no Go literal preceded it.",
"media.streams_playing": "BORN AS A KEY (v0.313.0, 2026-10-15, R-1028/R-1023) — the Plex claim on the running server and the media restart's stream check; no Go literal preceded it."
"media.streams_playing": "BORN AS A KEY (v0.313.0, 2026-10-15, R-1028/R-1023) — the Plex claim on the running server and the media restart's stream check; no Go literal preceded it.",
"app_page.tab_settings": "BORN AS A KEY (v0.315.0, 2026-10-15) -- the app page's tab bar. One literal key per tab, taken in Go (appTabLinksLang) and not composed in the template, so the marker-coverage gate can see it. Pinned by TestAppPage_DeployedDefaultsToSettings and the app_settings_* parity fixtures.",
"app_page.tab_data": "BORN AS A KEY (v0.315.0, 2026-10-15) -- the „Adatok es mentes\" tab's label. New copy: no page carried this name before the six app pages became four tabs.",
"app_page.tab_guide": "BORN AS A KEY (v0.315.0, 2026-10-15) -- the „Utmutato\" tab's label. New copy.",
"app_page.tab_logs": "BORN AS A KEY (v0.315.0, 2026-10-15) -- the „Naplo\" tab's label. The logs PAGE said „Naplok\" (plural); the tab is one app's log, so the word is new, not moved.",
"err.after_start.failed": "BORN AS A KEY (v0.315.0, 2026-10-15) -- the generic refusal for an after-start action that fails without naming its own sentence. Plex's three messages (err.plex_claim.*) are unchanged; this is the fallback a future app gets for free.",
"page.title.app_data": "BORN AS A KEY (v0.315.0, 2026-10-15) -- the data tab's page title. It replaces page.title.tier2_config, whose page no longer exists; the old key was removed in the same commit.",
"page.title.app_guide": "BORN AS A KEY (v0.315.0, 2026-10-15) -- the guide tab's page title. New: the details page it replaces had no title key of its own, it used the app's display name."
},
"flash.share.already_on": "A megosztás már be van kapcsolva.",
"flash.share.enable_failed": "A megosztás bekapcsolása nem sikerült.",
@@ -336,9 +343,6 @@
"page.title.app_settings": [
" — Beállítások"
],
"page.title.tier2_config": [
"2. mentés beállítása — "
],
"logs.fetch_failed": "Hiba a naplók lekérésekor: %v",
"storage.bar_purpose": "Külső adattároló — a telepített alkalmazások nagy méretű fájljai (média, dokumentumok) ide kerülnek; az adatbázisok a belső SSD-n vannak.",
"deploy.path_not_allowed": "hálózati tárhely — alkalmazáshoz nem választható",