- Overview jobs: Change the playlist, Add or remove a HyperDeck, Add a MIDI link, Add a computer, Make a PC program startable; 'Add a key for it' on unwatched Companion connections. - Computers > Setup: steps with a [how] each and the set-up scripts generated per computer by settings/scripts.py from the templates in remote-access/ (no site-shaped value left in them); Remove this computer drops the fixes and checks that used it. - Site setup > Site: the running and staged code, Install the staged folder (a one-shot launchd job running install.sh --keep-config, refused while live), Export site bundle (zip), New campus from a bundle (this campus's site block stays; every copied computer is flagged until touched). - sites/: na -> the repo config, _template = the empty campus; install.sh --site <id>. - Review reads appended checks as 'added'; tests for all of it. - Deployed page-only to NA Ingest. (config.json, status_panel.py and readiness.py are left to the READY-page work in progress in the same tree.) Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
541 B
541 B
Sites
One folder per campus. na/config.json is North Attleboro (a link to the repo's config.json, which install.sh
installs by default). _template/config.json is the empty campus: the three fixed keys, this Mac's record and
nothing else; install.sh --site <id> installs sites/<id>/config.json when the folder exists, otherwise the
template. The settings page's Export site bundle (Site setup > Site) gives you a zip to drop in as sites/<id>/;
its New campus from a bundle starts a campus from another campus's bundle.