mirror of
https://github.com/rcourtman/Pulse.git
synced 2026-10-26 13:39:47 +00:00
rcourtman
72bfeee246
A paid key activated on the public community build unlocks only the licence-gated features compiled into that build. Patrol modes, container update risk, Audit, RBAC and Reporting need the private Pulse Pro runtime, and the only way to get it was the download portal. Licence data from 14 October shows 6 of 36 v6 buyers and 39 of 109 migrated v5 licences still running only the community build. GET /api/updates/pro-runtime reports whether this install can switch, and POST /api/updates/pro-runtime/apply performs it. The license server download broker decides eligibility from the activation's licence, the same broker the Pro binary already updates from, so a refusal there reads as not_eligible and any other failure as unavailable. Without an activation the check answers not_activated without a network call. The in-place switch is limited to systemd and Proxmox LXC installs. It runs through ApplyUpdate with an explicit SwitchToProRuntime flag, so ordinary community updates never take the broker path. It accepts the Pro build of the running version or newer, refuses an older pin, and keeps the signed-archive, hash, self-test, backup and history-rollback steps of a normal update. Docker installs get the broker's digest-pinned image commands instead. The Settings card that uses these routes follows separately.