docs: record live Phase 25.5b sync verification
- update plan with live portal route deployment status - document fixed Pi sync blockers and successful round-trip test - refresh passing test count after runtime sync coverage additions Co-authored-by: Copilot <[email protected]>
This commit is contained in:
@@ -1558,9 +1558,15 @@ updates its display-facing values without a manual restart once sync lands.
|
|||||||
|
|
||||||
#### Validation
|
#### Validation
|
||||||
- Added runtime reload tests for `Account`, `Car`, and the sync callback path
|
- Added runtime reload tests for `Account`, `Car`, and the sync callback path
|
||||||
- Existing suite still passes (`66 passed`)
|
- Existing suite still passes (`67 passed`)
|
||||||
- Remote deployment / live portal-path verification still recommended whenever the
|
- **Live 2026-08-10 verification**:
|
||||||
server portal is updated
|
- deployed the portal page to unraid and confirmed `/settings/device` routes to login (`302`)
|
||||||
|
- fixed two real sync blockers on the Pi: reuse `db/upload_creds.env` and send
|
||||||
|
the server's required `X-Device-Name` / `X-Api-Key` headers
|
||||||
|
- enabled **Sync with server** on the Pi, changed `owner_name` on the server,
|
||||||
|
waited through the sync thread's 60-second offline/backoff window, and
|
||||||
|
observed both `GET /api/device-config` and the rendered topbar username on
|
||||||
|
the Pi update to `quoije-sync-test`, then revert cleanly to `quoije`
|
||||||
|
|
||||||
---
|
---
|
||||||
|
|
||||||
|
|||||||
Reference in New Issue
Block a user