Add canonical boot configuration synchronization

This commit is contained in:
v3d 2026-06-30 16:29:51 +02:00
parent 254a9b9cf3
commit eda151065c
14 changed files with 424 additions and 50 deletions

View file

@ -43,10 +43,20 @@ sudo ./install.sh --repair # repeat deployment without replacing gallery conten
```
The installer defaults to the user that invoked `sudo`, not to a hard-coded
`pi` account. To customize paths, startup mode, hotspot SSID, or Wi-Fi
interface, copy `pivilion.conf.example` to `/boot/firmware/pivilion.conf` (or
`/etc/pivilion.conf`) and edit it before installing. The hotspot is intentionally
open and passwordless.
`pi` account. The installer automatically creates `pivilion.conf` at the
externally visible root of the FAT boot partition, using the current system and
saved Wi-Fi settings. Linux may mount that same root as `/boot` or
`/boot/firmware`; users never need to expose that distinction. The hotspot is
intentionally open and passwordless.
The boot file controls startup mode, upstream Wi-Fi SSID and PSK, Wi-Fi country
and interface, hotspot name and channel, hostname, Pivilion user and paths,
generator state, and PHP upload limit. Pivilion commands keep it synchronized.
An 863-character Wi-Fi password entered there is replaced at boot with its
derived 64-character WPA PSK. The PSK does not reveal the original text, but it
still grants network access and must be treated as a secret. Invalid offline
edits retain the root-protected last-known-good settings and create
`pivilion-error.txt` beside the boot configuration.
Use `pikey` to save upstream Wi-Fi credentials, then `onion` and reboot to host
through Tor. Use `hotspot` and reboot to run the local captive gallery at