Replace polling with websocket live sync
This commit is contained in:
@@ -5,12 +5,13 @@ Updated: 2026-04-02
|
||||
## Active
|
||||
|
||||
1. Keep replacing remaining seeded fallback signals with runtime-backed 3proxy data and extend the Docker-verified ingestion path beyond access-log-derived usage.
|
||||
2. Harden websocket-driven live sync and keep forms/edit flows resilient to concurrent runtime updates.
|
||||
|
||||
## Next
|
||||
|
||||
1. Wire real counter/log ingestion into dashboard traffic and user status instead of seeded snapshot values.
|
||||
2. Refine Docker/runtime behavior and document real host-access expectations and deployment constraints.
|
||||
3. Expand validation and tests around service mutations, credential safety, and runtime failure reporting.
|
||||
3. Expand validation and tests around service mutations, credential safety, websocket reconnect behavior, and runtime failure reporting.
|
||||
|
||||
## Done
|
||||
|
||||
@@ -38,3 +39,6 @@ Updated: 2026-04-02
|
||||
22. Restored editable proxy endpoint in panel settings so copied proxy URLs and displayed user endpoints can be corrected from the UI.
|
||||
23. Replaced seeded dashboard/user usage with live 3proxy access-log ingestion, derived user traffic/status from runtime logs, and added frontend polling so the panel refreshes runtime state automatically.
|
||||
24. Verified the new runtime-backed snapshot flow in Docker by sending real traffic through the bundled 3proxy services and observing live byte counters in `/api/state`.
|
||||
25. Replaced frontend polling with websocket live sync over `/ws`, sending only changed top-level snapshot sections while keeping the current `http/ws` path compatible with future `https/wss` deployment.
|
||||
26. Stopped incoming runtime sync from overwriting dirty Settings drafts and added hash-based tab navigation so refresh/back/forward stay on the current panel tab.
|
||||
27. Verified websocket delivery in Docker over plain `ws://127.0.0.1:3000/ws` by authenticating, receiving `snapshot.init`, mutating panel state, and observing a follow-up `snapshot.patch`.
|
||||
|
||||
Reference in New Issue
Block a user