archipelagoandClaude Opus 5
6ba0599639
Demo images / Build & push demo images (push) Failing after 2m13s
The repo is source code and guidelines only. Nothing about how Archipelago's own fleet is run, or how the team works, stays in it. Untracked (kept on disk, gitignored) — 250 files: - .planning/ (199) and loop/ — internal development process - fleet operations tooling that targets specific nodes: deploy-to-target, deploy-tailscale, deploy-config-defaults, setup-target-dev, setup-aiui-server, setup-https-dev, debug-frontend, node-profile, fleet-fips-pair/unpair, image-recipe/sync-from-live.sh - image-recipe/INTEGRATION-GUIDE.md and docs/multinode-testing-plan.md, both of which are live-server workflow and fleet node inventories - the Phase 10 on-node verification and evidence records, which cite .planning/ as their evidence base KEY-05-ENTROPY-ENFORCEMENT.md was initially moved out with the other Phase 10 docs and then put back: it is cited as normative rationale from ten places in the codebase, including core/clippy.toml, which bans rand::thread_rng and points at it for the reason. That makes it a guideline, not an internal record. Node names removed from source (48 occurrences across comments, manifests and test fixtures): archi-dev-box, archy-x250*, shorty-s, framework-pt, zaza-optiplex, archi-thinkpad. Comments keep the engineering context and the date, which is what carried the meaning; the machine name did not. Three of those were live test values rather than comments and were replaced with valid stand-ins, not prose: two mDNS hostnames and a mesh peer name. An earlier pass substituted "a test node" into a hostname assertion, producing an invalid hostname; caught and fixed as test-node.local. Wipe mechanism: .local-only/manifest.txt inventories every local-only path and .local-only/wipe.sh deletes them on one confirmation, refusing to touch anything git still tracks. Both are themselves untracked, so the public repo does not carry a map of internal filenames. Verified: cargo check -p archipelago --all-features clean; archipelago-container 75/75 tests pass; appOrigin vitest 7/7; audit-secrets 5/5; every relative link in tracked markdown resolves (0 broken). Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
49 lines
2.5 KiB
Desktop File
49 lines
2.5 KiB
Desktop File
[Unit]
|
|
Description=Archipelago Kiosk (X11 + Chromium)
|
|
After=archipelago.service systemd-user-sessions.service network-online.target
|
|
Wants=archipelago.service network-online.target
|
|
ConditionPathExists=/usr/local/bin/archipelago-kiosk-launcher
|
|
Conflicts=getty@tty1.service
|
|
|
|
[Service]
|
|
Type=simple
|
|
# Wait up to 5 min for archipelago to serve /health. On slow hardware
|
|
# first-boot is dominated by the FileBrowser pull (unbundled ISO),
|
|
# initial archipelago state sync, and frontend settle — .198 took
|
|
# longer than 120s and chromium launched against an empty backend,
|
|
# producing a white window that only recovered on reboot. 300s gives
|
|
# slow-but-functional hardware enough headroom; TimeoutStartSec is
|
|
# bumped in lockstep so systemd doesn't kill us mid-wait.
|
|
ExecStartPre=/bin/bash -c 'for i in $(seq 1 150); do curl -sf http://localhost/health >/dev/null 2>&1 && break; sleep 2; done'
|
|
# Also wait for the web-ui asset swap to finish. The first-boot rsync into
|
|
# /opt/archipelago/web-ui is non-atomic and writes the large bg-*.webp images
|
|
# last — a kiosk launched mid-swap rendered the UI with blank backgrounds
|
|
# (CSS background-image 404s are never refetched). A representative large
|
|
# asset answering 200 means the swap is effectively done. Bounded 60s so a
|
|
# renamed asset can never block kiosk startup.
|
|
ExecStartPre=/bin/bash -c 'for i in $(seq 1 30); do curl -sf -o /dev/null http://localhost/assets/img/bg-home.webp && break; sleep 2; done; exit 0'
|
|
ExecStart=/usr/local/bin/archipelago-kiosk-launcher
|
|
TimeoutStartSec=360
|
|
Restart=always
|
|
RestartSec=5
|
|
|
|
# Resource guardrail (#36). On GPU-less / headless hardware chromium could spin
|
|
# software compositing at ~92% of a core, saturating the node and starving the
|
|
# backend (it caused the .198 receive timeout + deploy storms). Cap CPU + memory
|
|
# so a runaway kiosk can never take the whole machine down; Delegate so the cap
|
|
# also binds the chromium/Xorg children in this unit's cgroup.
|
|
# CPUQuota=75% (0.75 cores) was too tight even for normal playback — the kiosk
|
|
# was throttled ~40% of the time, which is what caused choppy HDMI audio on
|
|
# a test node (2026-06-28 incident). 200% (2 cores) gives enough headroom.
|
|
Delegate=yes
|
|
CPUQuota=200%
|
|
# Raised from 1500M/1200M: a Framework (Tiger Lake) kiosk sat at 806M used /
|
|
# 1.1G peak, riding the old MemoryHigh reclaim-throttle line — the throttling
|
|
# itself was the perceived UI lag. Keep Max well above real peaks; High stays
|
|
# the soft reclaim line so a runaway kiosk still can't take the machine down.
|
|
MemoryMax=2800M
|
|
MemoryHigh=2200M
|
|
|
|
[Install]
|
|
WantedBy=multi-user.target
|