4 Commits

Include renames

Author	SHA1	Message	Date
aaaamoooo	0037116edc	feat: manual landing endpoints for forward nodes (item 8) ... A forward node's exit target is now a choice: a managed panel server (existing behavior) or a manual landing endpoint — address + port + protocol (VLESS / SS2022 / SOCKS5) + operator-supplied credentials, including third-party nodes the panel does not run. The panel only builds the entry-side sing-box outbound and route rule; there is no exit resource, no exit job, and the node is exit-ready by definition. - model: Node.ExitMode/ExitAddress; manual exits force fixed port mode and skip the exit-server port table entirely - validation: address/port required; per-protocol credential presence; SS2022 passwords must be base64 key material of the method's key length (one PSK segment or serverKey:userKey) — the exact form sing-box accepts, rejected up front instead of failing at deploy - orchestration: resource building, deploy validation and rebuilds all branch on manualExit; switching managed->manual queues removal of the old exit resource, manual->managed mints a fresh exit resource id (deploy validation previously dereferenced the nil exit server — regression test locks the fix) - UI: exit target segmented control, link paste box that parses vless:// / ss:// / socks5:// links into the form, per-protocol credential fields (blank keeps the stored value on edit) - golden: new manualCreate/manualAssign/manualDeploy/manualJobs/ manualNodes sections — exactly one entry-side job whose outbound targets the manual address; all prior sections unchanged - the generated combined sing-box config passes the real sing-box 1.13.21 check	2026-10-21 11:18:00 +08:00
aaaamoooo	d316d0f8bb	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-21 11:18:00 +08:00
aaaamoooo	d287bb9be9	feat(panel): reskin backend — node sortIndex, presence/speed, /api/system, credentials, subscription aggregation (Node+Go parity)	2026-10-21 03:16:30 +08: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