admin
e66d4669d6
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
36 lines
1.5 KiB
Go
36 lines
1.5 KiB
Go
package web
|
|
|
|
import (
|
|
"strings"
|
|
"testing"
|
|
|
|
"gitea.dooplex.hu/admin/felhom-controller/internal/stacks"
|
|
)
|
|
|
|
// Decision 28 on the page: an unhealthy stop offers START (its way back) and no Mentések; the badge
|
|
// does not say "restore needed". Render test per branch.
|
|
func TestD28_UnhealthyStopPageOffersStart(t *testing.T) {
|
|
st := ubStack(nil, map[string]string{"web": "nginx:1.27"}, "2026-07-18")
|
|
st.Name = "bookstack"
|
|
st.State = stacks.StateStopped
|
|
st.HoldReason = "STOPPED BY THE BOX"
|
|
st.HoldKind = "unhealthy_stop"
|
|
h := renderBackupPage(t, "stacks", ubStacksData(st))
|
|
if !strings.Contains(h, `data-unhealthy-stop="true"`) || !strings.Contains(h, `stackAction(event, 'bookstack', 'start')`) {
|
|
t.Fatal("the unhealthy stop must show its sentence and a Start button")
|
|
}
|
|
if strings.Contains(h, `data-held="true"`) || strings.Contains(h, "visszaállítás szükséges") {
|
|
t.Fatal("an unhealthy stop is not a restore case")
|
|
}
|
|
a := renderBackupPage(t, "app_settings", appInfoData(st))
|
|
if !strings.Contains(a, `data-unhealthy-stop="true"`) || strings.Contains(a, `data-held="true"`) {
|
|
t.Fatal("app page: wrong branch for an unhealthy stop")
|
|
}
|
|
// positive control: an UPDATE hold keeps the restore branch
|
|
st.HoldKind = "update_failed"
|
|
h2 := renderBackupPage(t, "stacks", ubStacksData(st))
|
|
if !strings.Contains(h2, `data-held="true"`) || strings.Contains(h2, `stackAction(event, 'bookstack', 'start')`) {
|
|
t.Fatal("an update hold must keep its restore branch and offer no Start")
|
|
}
|
|
}
|