Binions installs and upgrades with apt — the standard Debian/Ubuntu package manager. There is no special updater and you never build from source. A normal apt update && apt upgrade is enough to move the whole platform to the latest release, and systemd restarts the affected daemons for you. This page covers the exact commands, what happens when you run them, and the two checkpoints to know about — the major-version gate and the post-upgrade checklist.
Take a backup first. An upgrade advances your live database and per-daemon state. Always capture a fresh snapshot before you upgrade — see Backup before upgrade. It takes seconds and is your only clean way back.
Binions ships as a small family of apt packages. There is one binions-<name> package per daemon — for example binions-logger or binions-mailbox — plus a single meta-package that depends on the whole set. Installing the meta-package pulls in every daemon at once, and upgrading it carries them all forward together. (The exact meta-package name is listed in the Installation section.)
The whole platform is built and tested as one release at one version, so every installed binions-* package should always report the same version number. You do not mix daemon versions on a single host — apt keeps them in step for you.
The simplest path is the one you already use for the rest of your system. Refresh the package lists, then apply available upgrades:
sudo apt update
sudo apt upgradeThis upgrades Binions alongside any other system packages. If you would rather review what is installed first, list just the Binions packages and their versions:
apt list --installed 'binions-*'To move Binions forward on its own — without touching unrelated system packages — restrict the upgrade to the binions-* set:
sudo apt install --only-upgrade 'binions-*'This upgrades every installed Binions package to the newest available release while leaving the rest of your system untouched. The meta-package keeps the daemons aligned, so they all land on the same version.
When the new packages install, the change is applied cleanly and in order:
binions-<name> package replaces its daemon binary on disk.Good to know. Within a single major line, upgrades are additive and backward-compatible — minor releases add features, patches fix bugs, and existing playbooks and config keep working. You rarely need to change anything; just read the release notes for the version you are moving to.
One upgrade can be stopped on purpose. A single licence (one set) covers a whole major line, so an upgrade that would cross into a new major version is intercepted by the major-version gate before anything changes. If you are not licensed for the newer major, apt refuses the upgrade and prints clear guidance — either hold your current version or buy the major upgrade. It never deletes data; it simply declines to install the newer major. Everyday minor and patch upgrades pass straight through.
Once the packages are in place, confirm the platform came back healthy. A quick first check is the rolled-up status view:
binions-cliconsole statusEvery daemon should report up and ready, all on the new version. Work through the full post-upgrade checklist to verify versions match, there are no restart loops, and the logs are clean. If something looks wrong, you can return to the previous version with the rollback procedure — after taking a backup.