Overview All guides ▾
Guides
- Customising BoothWallYou want your own wall: the config file, the brand images, the themes, the copy.
- Running an eventThe day itself: the remote, the Control panel, what the hosts do when a photo arrives.
- Upgrading older review settingsUpgrading saved review settings to standalone manual approval.
- DevelopmentWorking on the code: the workspace, the gates, how the pieces run from source.
- Architecture notesThe decisions behind the code and why they were made.
- Building for Vega OS: notes from the fieldWhat we learnt about Vega OS, the Virtual Device and the Fire TV Stick along the way.
Upgrading an existing install
- Migrating saved settings to file authorityOlder installations may have presentation values saved in the database. Those values can override file defaults. Back up the database and photo storage before an upgrade. Do not delete the saved settings row to make a new config take effect: it can contain branding, category identities and live playback/upload state.
- Updating client fingerprintsMigration
0009_client_fingerprints.sqlchanges how the API identifies clients for abuse limits. New records use a daily, purpose-separated HMAC. The server key prevents someone with only a database copy from enumerating IPv4 addresses using the old public date salt. These identifiers are pseudonyms, not anonymous data. Existing records keep their current cleanup lifecycle.
Apps and packages
Each app and package has its own README beside its package.json.
Rather not run servers? BoothWall Cloud hosts it for you. These docs cover the open edition only.