fix: reuse upload credentials for device config sync

- load server sync creds from db/upload_creds.env like uploads do
- fall back from YARIS_DEVICE_KEY to existing YARIS_API_KEY
- document shared credential flow for server-synced identity
- add test coverage for sync credential fallback

Co-authored-by: Copilot <[email protected]>
This commit is contained in:
Mathieu Moran
2026-08-10 17:37:52 -04:00
co-authored by Copilot
parent 585da18225
commit 5a5058adca
4 changed files with 30 additions and 5 deletions
+6
View File
@@ -203,6 +203,12 @@ nano /home/yaris/app/yaris-obd/config/device.json
- **`device_name`**: Reserved for server-side display (Phase 25.5 feature, not yet used)
- **`avatar_path`**: Avatar image shown in topbar; must exist in `static/img/` (replace `static/img/yaris.png` with your own image, or point to a different file)
If you want the remote server to become the source of truth instead, keep the Pi
upload credentials in `db/upload_creds.env` (`YARIS_SERVER_URL` + `YARIS_API_KEY`)
and enable **Sync with server** in the local Settings page. The same creds file is
reused for config sync; when the server pushes new identity values, the running Pi
UI hot-reloads them on the next successful sync.
After editing, restart the app:
```bash