feat: seed a default profile at first boot
A store with no profile gets a default one, using the seed POST /profiles already creates plus a starter palette. db/ now holds those records instead of stored data, and the unused db/presets/*.bin files are gone. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
1 parent
b6aa0635ae
commit
190c8bc982
62 files changed
+51
-124
No files matched your search
@@ -24,7 +24,7 @@ make test-browser HOST=<ip> # Selenium UI tests (needs selenium and chromedriv
|
||||
- `led-driver/` (submodule): MicroPython firmware for the ESP32 LED drivers.
|
||||
- `led-tool/` (submodule): `led-cli`, configures drivers over serial and updates the controller over Ethernet (`led-cli --ota HOST`).
|
||||
- `led-simulator/` (submodule), `espnow-sender/`: test helpers.
|
||||
- `db/`: stored zones, presets and devices, importable with `PUT /db/<name>`.
|
||||
- `db/`: the records a controller starts with (the `default` profile the firmware seeds at first boot, plus pattern metadata), importable with `PUT /db/<name>`.
|
||||
- `test/api/`: the API tests (`test/api/README.md`); `test/browser/`: the UI tests.
|
||||
|
||||
## Docs
|
||||
|
||||
Reference in new issue
Block a user