Scaling (IaC/queue groups), self-signed CA auto-trust + public-IP SANs, clean uninstall #9
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?
Scaling, self-signed trust, clean uninstall, and IaC.
Self-signed TLS / agent trust
GET /api/enrollment/ca.ServerCaAutoInstall) and keep it current across renewals — ordinary system validation then trusts a direct/local connection. It is not pinned or forced: add a reverse proxy with a real certificate later and that validates normally, the self-signed CA just goes unused.configure --install-server-ca, agent MSICAINSTALL, ADMX toggle, install scripts. Accept-any (TlsSkipVerify) remains an escape hatch.hostname.<dns-suffix>for every adapter suffix + the global domain, every non-link-local IP on every adapter, the discovered public IP (cloud metadata → echo, time-bounded, self-signed only),PUBLIC_SERVER_URLhost, and localhost/loopback.Clean uninstall
ExecuteR-Server.exe purgeand the server MSI's "Also remove all data, keys and self-signed certificates" checkbox /PURGEDATA=1forget the managed chain from the Windows stores and delete generated data/logs/secrets. A plain uninstall still keeps everything for a resume.Scaling
compose(moved from root, deploy.sh + docs updated),swarm(replicated stack, bind mounts on shared storage, 3-node JetStream cluster, API replicas + single scheduler worker), andk8s(StatefulSets, Deployments + HPA, single worker, ingress). Wiki gains a Scaling and HA page with an HA topology diagram and the stateless/stateful breakdown (NATS cluster/supercluster, Tailscale/NetBird overlay, MicroCeph shared storage, service discovery).Verified locally: solution builds, Backend 100 / Agent 60 / Shared tests pass, svelte-check clean, agent + server MSIs build, self-signed boot emits the broadened SANs incl. the public IP. Dev commits used
[skip ci]; this PR is where CI runs.🤖 Generated with Claude Code
On Windows the managed chain is located in the machine certificate stores by subject and reused across reinstalls; a plain uninstall left the certs and the generated data/logs/secrets/appsettings behind. New `ExecuteR-Server.exe purge [--yes]` forgets the chain (removes root/intermediate/leaf from the stores) and deletes the generated runtime state, keeping MSI-owned files. The server MSI adds a PURGEDATA property, an uninstall-page checkbox ("Also remove all data, keys and self-signed certificates") spliced into the maintenance flow, and a deferred CA that runs purge --yes before RemoveFiles when checked. A plain uninstall still keeps everything for a resume. Verified: purge deletes data/logs/secrets/appsettings/nats.conf and keeps nats-server.exe; MSI builds clean with the property, CA and PurgeDlg present; solution builds, 99 backend tests pass. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>