Update routes and rollback overview
Prerequisites and authority
Local installation authority, a complete approved release package, working Docker and access to the deployment record are required. Preserve existing data before installation/update/removal.
Choose an update route
Updates may use a packaged local archive or the installed control/update route. Use only combinations supported by the target release. Both routes must preserve the same installation identity, persistent storage and deployment configuration.
Manual approval is the documentation default. Silent updates are limited to releases and installations explicitly eligible under the release policy. A version being labelled minor does not, by itself, authorize an unattended migration.
Before approving an update, review compatibility, migration requirements, expected interruption, backup availability and recovery procedure. Confirm the installed and target versions and verify the archive/manifest integrity.
Both update agents use rollback-safe verification before reopening normal application traffic. After reopening traffic, automatic database rollback is skipped to preserve possible new writes; a subsequent failure requires recovery. Offline update handoff uses the agent bundled with the selected release, not an arbitrary newest agent from the Internet. Online updates use the installed agent. See Product updates, compatibility and rollback for the Windows and Linux procedures.
After updating, verify API health, administrator access, customer access, workers, router reconciliation and one representative payment/subscription journey. Capture the applied version and outcome.
If rollback begins, stop unrelated changes and use Product updates, compatibility and rollback/Update, license validation or service reachability issue. Do not alternate installers and manual image replacement to force the deployment forward. An update that reports success but leaves failed workers or inaccessible routers is not operationally accepted.
Related guides
Related guides: First-deployment walkthrough and success checklist, Deployment verification and first login, Back up BryanNet and validate backups, Restore BryanNet safely, Product updates, compatibility and rollback.