Upgrade Guide
Less than 1 minute
Upgrade Guide
1. Upgrade Flow
2. Pre-upgrade Checklist
| Item | Requirement |
|---|---|
| Release notes | Confirm incompatible changes, SQL scripts, and dependency changes. |
| Database backup | MySQL backup is complete and restorable. |
| File backup | Uploaded files, images, certificates, and local storage are backed up. |
| Configuration backup | Environment variables, Nginx, broker, ZLM, and scheduled-task configs are saved. |
| Rollback package | Previous backend and frontend packages are retained. |
| Maintenance window | Users and project stakeholders know the upgrade window. |
3. Upgrade Verification
| Area | Verification |
|---|---|
| Login and menu | Users can log in and menus load normally. |
| Product and device | Product list, device list, and device detail are normal. |
| Device access | MQTT or real device reporting works. |
| Rule and scene | Existing automation still triggers correctly. |
| Video | Live view, playback, and channel status are normal if enabled. |
| Reports | Data center and report export are normal. |
| Permissions | Ordinary users cannot access unauthorized data. |
4. Rollback Notes
Rollback must consider code, database, frontend assets, cache, and message broker status together. If SQL changes are not backward compatible, restore the database backup rather than only replacing application packages.