Update

Each day the server renews its licence, and the answer names a newer release on its channel when there is one. System › License then shows it with its notes. There are three ways to install it, and they all run that version's own installer:

Way	How
From the interface	An admin clicks Update to … under System › License
By itself	Security releases install themselves, unless FLOWTRIX_AUTO_SECURITY_UPDATES=false in .env
On the server	The command System › License shows: curl -fsSL https://get.newiq.pl/flowtrix/<version> | sudo bash, pressing Enter at the key question to keep the server's activation

Whichever way:

• the images are pulled by the digest the release names, and checked;
• the configuration, .env and data stay;
• a version older than the one running is not installed, because the store's changes do not run backwards;
• if the new version does not come up healthy, the version before is put back.

The outcome shows on System › License. On the server:

journalctl -u flowtrix-update      # the updater
cat /opt/flowtrix/update/log       # the installer's output of the last update

Beta or stable

A server installed from a beta keeps getting betas; one installed from a stable release gets stable releases. The plain get.newiq.pl/flowtrix serves only the newest stable, so a beta server is updated with the version named. See Updates and channels.

Without systemd

The updater on the host is a systemd service (flowtrix-update.path). Without systemd, System › License offers the command only.