5 Commits

Include renames

Author	SHA1	Message	Date
aaaamoooo	05366d9177	perf(panel): kill per-request full-database clones (item 22, backend) ... Data.Clone() was a full JSON marshal/unmarshal round trip (with a per-record map dance for unknown fields): 6.3ms and ~13.8k allocs per call on sandbox hardware, and every admin GET paid it at least twice (RequireAdmin's user lookup + the handler). Clone is now a reflective deep copy of the plain data graph — byte-identical output, proven against the JSON clone on the real seed database by TestCloneEquivalence — at 0.37ms / 538 allocs. CurrentAdmin resolves the session user under a read-only store View and no longer clones at all, so an admin GET takes exactly one snapshot. Sandbox benchmarks (11 servers / 26 customers / 25 nodes): overview 17.2ms -> 0.38ms, servers 13.3 -> 0.85ms, customers 20.5 -> 1.54ms, nodes 15.8 -> 3.45ms, jobs 13.0 -> 0.39ms per request.	2026-10-21 10:50:00 +00:00
aaaamoooo	2fafd85d1f	feat(panel): build-before-bind + socks5 fixed node account (items 20+21) ... Item 20: drop the zero-client deploy gate in ValidateNodeDeploy for all protocols, stop RebuildNode from auto-removing a node whose bindings reach zero, and let server/heartbeat reconciliation rebuild zero-client nodes like any other. Nodes are built and deployed first; bindings can be added and removed freely. Item 21: socks5-auth nodes carry one node-level fixed account (node.socksUser/socksPassword, minted at creation or by the store-load migration MigrateSocksNodeCredentials, idempotent). The sing-box inbound's only user is that pair regardless of bindings; subscription links for every bound customer carry the same pair. The generated username avoids the ng: prefix so the agent never attributes the account's traffic to a customer — it stays on the node's inbound counters. Edit form shows both fields (copyable) for socks nodes; NormalizeNode validates operator-supplied usernames.	2026-10-21 10:40:58 +00:00
aaaamoooo	ad18e16ac6	feat: customer-level credentials shared across all nodes (item 2) ... One credential set per customer (UUID + 32-byte root relay key + shortId) lives on the customer record; node bindings no longer store credentials. SS2022 user keys derive deterministically from the root key by method length (16/24/32-byte prefix), so a single password serves every protocol, matching 3x-ui's per-client credential model. Reality public keys stay a node property and are shown per binding in the credentials pane. - store: load-time convergence — first binding's set wins; a converged password that is not a 32-byte root key is regenerated (uuid/shortId preserved); bindings are stripped; idempotent, covered by tests - deploy: the orchestrator stamps the customer's set onto a build copy; subscriptions resolve the same set; the derivation applies in both the inbound builder and the URI builder (verified live: Alice's N1 link is byte-identical to the pre-change seed expectation, her N2 user key is exactly the root key's 16-byte prefix) - API: GET /api/customers/:id/credentials returns {credentials, bindings}; regenerate is now POST /api/customers/:id/credentials/regenerate and rotates the whole set, rebuilding every deployed node of the customer - UI: credentials pane shows the single shared set plus per-binding node/protocol/Reality-public-key rows - golden subscriptions fixture regenerated under one shared set (RF and SS entries byte-identical to before; five entries audited by hand) - golden baseline re-captured for the new shapes; difftest normalizer now treats a base64 root key's prefix-truncation encodings and the Surge '='-mangled variants as the same secret	2026-10-20 21:21:13 +00:00
aaaamoooo	011eecc096	feat(panel): reskin backend — node sortIndex, presence/speed, /api/system, credentials, subscription aggregation (Node+Go parity)	2026-10-20 18:09:07 +00:00
aaaamoooo	3951134940	feat: Go port of the panel in panel-go/ — drop-in replacement for server.js ... Pure-stdlib Go implementation of the whole control plane: same nexusgate.json schema (unknown fields preserved verbatim, explicit null/false tri-states modeled), same HTTP API and error strings, embedded frontend (NG_PUBLIC_DIR override), self-implemented scrypt auth, X25519 Reality keys, panel-hosted keyStore and heartbeat reconciliation included. Version stays 0.6.8. Verified: Go tests 33/33 (scrypt + Reality vectors generated from the Node implementation, subscription goldens byte-identical), Node suite 52/52 untouched, differential E2E against the Node panel 50/50 including two-way DB swap. See panel-go/PARITY.md and panel-go/INSTALL-GO.md.	2026-10-20 08:21:54 +00:00