`inbuxa upgrade [server|console|webmail] [--dry-run] [--yes] [--no-backup]`
moves what is installed to the releases this installer pins; a newer
installer is what brings newer releases. What is installed is read from
the machine: the image tags in compose.yaml, the server binary's
--version, the console's release marker, the webmail's VERSION. status
now shows each component's version, and what this installer would make
it.
One component at a time, the server first, each checked once it is
running again and put back if not, which stops the upgrade:
- a container by its tag in compose.yaml, and its old tag to undo it;
- the server on the host keeps its old binary as inbuxa-server.<version>;
- the console and the webmail on the host keep their old directory until
the new one is in and, for the webmail, answering; its environment's
IHASMAIL_VERSION follows the files.
Before the server, which may convert its store on first start, it is
stopped and its own data archived into <dir>/backups -- the volumes with
the server's own image, or <dir>/server -- unless --no-backup. A store kept
elsewhere is said to be backed up where it lives.
The release marker now records the version beside the checksum, and
"local" for a tarball given by hand, which upgrade always replaces.
Options and components can come in any order.
Tests: the plan read from compose.yaml and the host's files, one image
tag changed and no other, a directory put back when its replacement
fails, options after components. e2e: upgrade-containers 17/17 (installed
by v2026.10.12.1; archive, new images, the same mailbox signing in, a
second run with nothing to do), upgrade-host-server 11/11 (a binary that
won't start put back with the server answering, then the real release
with the old binary kept and the data archived), upgrade-frontends-host
10/10 (older tarballs to the releases, the webmail answering as its new
version, the console still pointed at the server). install-local,
install-host, webmail-host, all-host and interface pass unchanged.