Before the update
- Check the source of updates and the selected version in the dashboard. Stable and pre-channels can contain different features.
- Make sure that backup storage, disk space and PostgreSQL tools are available.
- Create a fresh backup copy of, check its integrity and save access to the server during the update.
- View the limitations and migrations of the selected release, then run the update in the panel.
What’s being tested
A modern official installer checks not only the SHA-256 of the archive, but also the signature of the checksum file. A missing or incorrect signature stops the installation. Disabling the check through a flag or environment variable is not a supported bypass. An old upgrader already installed may not have this verification. When switching from an old installation, use the current official installer from a trusted source; having a signed archive does not in itself update the verification script.Procedure for updating
For the database archive, the installer first triespsql, pg_dump and pg_restore.
The pg_dump version must not be lower than the main version of PostgreSQL.
For external databases need working client tools and access configured
AXOTTLE_DB_URLThe neighboring old Docker container is not selected by name only:
Backup path through Docker checks published loopback port and base name
with the panel plugged in.
The verified update dump is stored separately from regular backups:
by default in /opt/axottle/data/backups/upgrades, the path can be set through
--backup-dir or AXOTTLE_UPGRADE_BACKUP_DIR. Save the dump together with the .meta;
The exact path is displayed in the update report.
- Before stopping and replacing the panel, the database archive is created and checked. If the preparation of the archive fails, the installed panel is not replaced.
- A set of the previous release is saved: binary, migrations, installation files and associated service release files.
- The service stops, the new kit is installed and started.
- Check the health of the running panel. If you fail, you start a coordinated rollback.
journalctl -u axottle.service will help distinguish between a new version failure and a recovery failure.
Verification
Verify the requested and actually running version, the completion of the operation and the availability of the dashboard. Check the database, agents and key pages./ping availability confirms the start of the process, but does not replace the validation of the desired work scenarios.
