maziggy 464d56ea0d fix(install): make SpoolBuddy kiosk usable on first boot in full-mode install ...

Full-mode install booted into an unusable kiosk:
  - Chromium opened before uvicorn → "can't connect to localhost"
  - After reload, requires_setup=true hijacked /spoolbuddy → /setup
  - Touch-only Pi has no keyboard to complete the setup wizard
  - Declining auth left the user at / instead of the kiosk

  Fixes, bundled:

  1. backend/app/cli.py kiosk-bootstrap now, in one DB transaction:
     - creates a scoped API key (can_read_status=True, rest false)
     - upserts setup_completed=true
     so AuthContext never redirects and the kiosk URL loads directly. Users
     who want auth can still enable it from the admin UI; the provisioned
     key keeps working.

  2. install.sh full-mode runs the CLI as the bambuddy service user after
     create_bambuddy_service and sed-replaces the CHANGE_ME_AFTER_SETUP
     placeholder in spoolbuddy/.env.

  3. The generated spoolbuddy-kiosk-launch polls ${backend_url}/health for
     up to 60s before exec'ing chromium, so cold boots wait for uvicorn
     instead of flashing ERR_CONNECTION_REFUSED.

  Standalone mode was unaffected — users supply a real key from their
  existing Bambuddy before install.

2026-04-18 08:14:53 +02:00

..

generate_splash.py

Polish SpoolBuddy boot splash and reduce initramfs rebuilds

2026-03-26 13:05:20 +01:00

install.sh

fix(install): make SpoolBuddy kiosk usable on first boot in full-mode install

2026-04-18 08:14:53 +02:00

splash.png

Polish SpoolBuddy boot splash and reduce initramfs rebuilds

2026-03-26 13:05:20 +01:00

spoolbuddy-idle.sh

.

2026-04-12 11:16:43 +02:00