5 Commits

Include renames

Author	SHA1	Message	Date
maeneko	5c3bf21918	Show each server's Forgetting version in the panel ... - awg-agent sends its install's VERSION (from the CLI's env, else the project's .env) in the auth frame; the hub keeps it in nodes.version (added by migration), so an offline node still shows the last one. - GET /ui/nodes returns version per server (0 is the panel's own) and the panel's version at the top. - ServerBar: a vX.Y.Z chip next to the AWG generation. A node older or newer than the panel, or one that sends no version (agent before 0.3.4, shown as v?.?.?), gets a warm chip with an "update it" tooltip. - App.css: tertiary-container tokens from design.md (light) and a warm dark pair; they did not exist yet. - Mock server: panel 0.3.3, Frankfurt behind on 0.3.2, Amsterdam with no version.	2026-09-27 18:03:57 +03:00
maeneko	eb0ec2878c	Bump to Beta 0.3.3 ... All seven places the version is written down: .env, the copy in install.sh, the four package.json files and the /ui/brand example in the README. Deleted devices get a signed 410 revoked with an echo of the request, so a client can tell a revoked key from a network failure; master-key peers no longer outlive their devices; API keys can manage master keys.	2026-09-27 16:23:02 +03:00
maeneko	3eede2f015	Bump to Beta 0.3.2 ... All seven places the version is written down: .env, the copy in install.sh, the four package.json files and the /ui/brand example in the README. A master key can serve its devices from several servers; a server that joins a core as a node keeps its own panel.	2026-09-26 21:44:25 +03:00
maeneko	2f2f0e268a	Bump to Beta 0.3.1 ... Covers all seven places the version is written down: .env, the copy install.sh keeps because it prints its banner and builds the release URL before the archive with .env exists, the four package.json files (awg-agent is new), and the /ui/brand example in the README. Multiple servers under one panel (core + nodes), the installer's role question and its full log.	2026-09-26 20:19:50 +03:00
maeneko	789538756a	Manage several servers from one panel: core + nodes ... A node is a VPN server without a panel. awg-agent on it dials the panel (core) over an outbound WSS connection and runs the panel's requests on its own awg-ctrl, which stays on 127.0.0.1 and is unchanged. No inbound port on the node, works behind NAT. - awg-ui/nodes.ts: node registry in ui.db, WSS hub on NODE_PORT with a self-signed cert whose SPKI pin goes into the join string, RPC with timeouts, health polling, /ui/nodes routes. - Nodes enroll with a one-time awgjoin:// string (secret stored hashed, 1 hour) and then authenticate by their own Ed25519 key. The agent checks the pin before sending anything and only forwards /health, /api/*, /awg/*. - server_id 0 is the panel's own awg-ctrl; LOCAL_NODE=off makes the panel run without a VPN of its own. The panel picks a server with X-Server-Id, API keys use their server_id. sen:// still serves one server. - UI: a card per server in the server bar, switching remounts the tab, «Добавить сервер» gives the join command. - CLI: agent service, roles from cli.env, join / unjoin commands. - Release archives include awg-agent.	2026-09-26 19:48:33 +03:00