julian
84f00db48b
Retention (keep-last / keep-daily-days) is operational policy the on-site admin should tune, not a server env var requiring a redeploy -- same reasoning that moved the target directory to the UI. - Migration 0017: site_config.backup_keep_last + backup_keep_daily_days (nullable; null = code default 7 / 30 per field). - BackupService reads retention fresh each run; status() exposes keepLast + keepDailyDays. DEFAULT_BACKUP_RETENTION is now a pure code default (env reads gone). - PUT /api/backup/config accepts keepLast / keepDailyDays (non-negative int, or null to reset to default; 400 on negative). - UI: two retention fields on the Backup config card; one Save covers target + retention. i18n sq + en. BACKUP_KEY wired into Komodo: - komodo/resources.toml: BACKUP_KEY=[[park_buzi_backup_key]] (per-booth secret, alongside JWT / signing keys). - komodo/.env.komodo.example: documents it as the ONLY backup env var -- escrow it offsite alongside EVENT_SIGNING_KEY (recovery needs both); target + retention are admin-chosen in the UI / DB, not env. Server .env.example trimmed to just BACKUP_KEY. Also carries the small in-progress setup-intro i18n copy trim. Tests: 218 server tests green, incl. retention persist / reset-to-default / reject- negative and the updated status shape. Migration applies cleanly (needed a statement-breakpoint between the two ALTERs). Wiki backup-recovery updated. Claude-Session: https://claude.ai/code/session_01Xcm6ikLgGoCxxHrxtjkk5V
komodo/ — fleet deployment as code
Infra-as-code for the Komodo Core control plane that deploys the parking appliance to the
booth fleet over the NetBird mesh. See wiki/decisions/fleet-deployment-komodo.md for the
rationale, threat-model analysis, and the three settled choices (many/growing fleet · deploys
are manual + pinned · secrets are Komodo-managed, per-booth).
This directory does not change how images are built or how the app runs — it's only the
control plane. The booth still runs the same docker-compose.yml + docker-compose.prod.yml
(container-deployment); Komodo just drives them remotely instead of someone SSH-ing in to
run booth.sh.
Files
resources.toml— the Komodo resource definitions (Servers, Stacks, optional Builders/ Procedures), synced into Core via a ResourceSync. This is the reviewable, version- controlled source of truth for which booth runs what..env.komodo.example— the variables a Stack expects, documenting what comes from Core's secret store (per-boothJWT_SECRET/EVENT_SIGNING_KEY) vs. plain Stack env.
How Core consumes this (one-time)
In Komodo Core, create a ResourceSync pointing at this repo + path (komodo/resources.toml),
on the branch you manage from (e.g. main). Core reads the file and reconciles Servers/Stacks to
match. Thereafter, a PR to this directory + a sync is how you change the fleet — no clicking.
Komodo's TOML schema evolves across releases. Treat
resources.tomlas a starting sketch:resources.tomlmirrors the workingpark-buziStack (built by hand in the Core UI, then exported to TOML — so field names match the running Komodo version, v2.2). Import it into the sync Unmanaged first and review the diff; it should be ~empty against the live Stack.
How servers get created — NOT here
There is no [[server]] block in resources.toml. Servers are created by the Periphery
agent onboarding outbound: in Core, create a one-time Onboarding Key (Settings →
Onboarding), then install Periphery on the booth passing --onboarding-key + --core-address
(Core's reverse-proxy URL, reached over the NetBird mesh) + --connect-as=<booth-name>. The
agent self-registers, generates its own auto-rotating key pair (private key never leaves the
booth), and connects outbound — the booth opens no inbound port. The sync owns only the
Stack, which references the server by the name it onboarded as (server = "park-buzi"). See
wiki/decisions/fleet-deployment-komodo.md.
Adding booth N
Copy the [[stack]] block, change name, server (its onboarded name), and the per-booth
secret references ([[park_<site>_jwt_secret]], [[park_<site>_event_signing_key]]). Create
those secrets in Core's store first.
Hard rules encoded here (do not relax without updating the decision page)
- No deploy webhook on a booth Stack. Deploys are a human action; pin
TAG=dev-<sha>before a production booth goes live. A moving:devon a production booth is the non-determinism we rejected. (TAG=devhere is fine while staging.) - Onboarding, outbound, mesh-only. Servers self-register via an onboarding key; Periphery connects outbound to Core's mesh URL and exposes no inbound port. Never a LAN/WAN address.
- Secrets are per-booth and unique.
EVENT_SIGNING_KEYsigns the anti-fraud ledger — one leak must taint one booth, never the fleet. Reference Core secrets by name; never inline a real value in this file (it's in git). - Volumes preserved. The Stack must never run
compose down -v— that would wipe theparking-datavolume (the signed ledger). Komodo's "destroy" is gated for the same reason.