Standalone NATS + install fixes, unified triggers, richer inventory & docs #11
Reference in New Issue
Block a user
Delete Branch "dev"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Rolls up this iteration of standalone-server, install, and UX work.
Standalone / NATS
Install / networking
Triggers & scheduling
Inventory & device UX
Docs and screenshots refreshed to match.
- The server MSI Network page now has a NATS "Bind" field (NATSBIND, default 127.0.0.1) alongside the ports; it flows through `setup --nb` into nats.conf. Set it to 0.0.0.0 only when an edge proxy on another host must reach NATS directly. (The backend still connects over loopback, so appsettings NATS_URL is unchanged.) - All NATS-related directories are grouped under data/nats: jetstream (store_dir ../data/nats, nats-server appends "jetstream"), resolver (../data/nats/resolver), and the auth secrets (../data/nats/secrets). db, keys and tls stay at the top of data/. - appsettings Urls is written as https when self-signed TLS is on, matching the actual listener (the backend already force-upgrades http->https at startup; the file just said http before). Verified: setup produces the data/nats layout and https Urls; boot creates data/nats/{jetstream,resolver,secrets} with nothing in C:\data; server MSI builds clean (setup CA 251 chars, under the ICE03 limit) with the NATSBIND field/property present. Backend 103 tests pass. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>When the NATS WebSocket bind is opened for a remote edge proxy (NATSBIND non-loopback) and self-signed TLS is on, the sidecar's WebSocket listener now serves TLS using the server's own managed leaf (data/tls/server.crt + .key) — no separate NATS certs to generate or rotate. The loopback default is unchanged (plaintext WS; the backend relays /messaging/* over loopback). - ServerCli nats.conf: core + monitor are backend-only and always loopback; only the WebSocket honours NATSBIND. Its block is `tls { cert_file; key_file }` from data/tls when exposed+self-signed, else `no_tls`. - appsettings NATS_WS_PROXY becomes wss when the WS runs TLS; NATS_TLS_CERT carries the cert path for the sidecar. - MessagingWsProxy trusts the loopback cert when relaying to a wss target (loopback can't be intercepted, so no CA distribution to the process). - NatsSidecar watches the cert and bounces nats-server on rotation (it reads certs only at start; the supervisor respawns it with the fresh chain). - MSI Network page: the bind field is labelled "WS bind" and its note makes clear core/monitor stay local. Verified: loopback stays no_tls/ws; exposed boot logs "Listening for websocket clients on wss://0.0.0.0:9222", monitor healthz 200, backend serves https://0.0.0.0:9080, NATS core connects over loopback, layout is data/nats/*. Backend 103 tests pass; server MSI builds clean. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>- The served Linux/macOS install script is normalized to LF. A CRLF bash script piped to bash fails with ": invalid option namepefail" (set -euo pipefail\r). BuildUnixScript now ReplaceLineEndings("\n"). - The reported build version drops the -<shortcommit> suffix: enrollment, presence, /health and the agent CLI now report 2026.08.10.0056, not 2026.08.10.0056-c87a8bf. The binary keeps its full informational version. - The device page labels the identifier "Client ID:" next to the value. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>The agent now reports a clean OS name and richer fields: - Caption is the base OS ("Windows 11", "Windows Server 2022") — "Microsoft " stripped and the edition split off (regex on the Win32 caption). - Edition is its own field ("Pro", "Enterprise", "Standard", ...). - ProductType added (Workstation / Server / Domain Controller) from Win32_OperatingSystem.ProductType; unix maps its Server/Workstation role. - ReleaseVersion added for Windows (DisplayVersion, e.g. "23H2") from the registry. The device OS caption is updated from the inventory report, so the device list and platform derivation show the base name too; the "Server" group rules still match. Device detail shows OS (release), Edition, Product type, Version. Dev seed data updated to exercise the new fields. Tests pass; svelte-check clean. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>