feat(dashboard): add local web UI for live config and component health#177
Open
onlymaj wants to merge 4 commits into
Open
feat(dashboard): add local web UI for live config and component health#177onlymaj wants to merge 4 commits into
onlymaj wants to merge 4 commits into
Conversation
Loopback HTTP server at 127.0.0.1:7878 for live config edits and per-component health dots. Hot-reload soft keys; rebuild proxy on hard keys via a new Supervisor.
Migrate existing configs on load; update env var, wizard, validator and dashboard. Move YouTube hint into a popover.
Group upstream_forwarder_url and forwarder_hosts under a new Upstream subtab; materialize defaults so missing keys still render. Drop a few redundant hint paragraphs.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
As open issues have grown, a visual way to inspect the running proxy was needed so users without log-reading skills can self-diagnose faster. The proxy was configured by hand-editing
config.json+ restart, and runtime health (blacklisted script IDs, Worker chain reachability, upstream forwarder status, MITM CA trust state) was only visible via logs. This adds a loopback dashboard at http://127.0.0.1:7878/ for live config edits and per-component status dots.What
update_confighooks onProxyServer/DomainFronter; hard keys (ports, host, auth_key, script_ids, google_ip, front_domain) trigger a brief proxy rebuild orchestrated by a newSupervisoros.replace) with rollback on validation or rebuild failure