Upgrade

Make a backup first. Database migrations are not reversible; a preflight check is not a backup or a promise that a later failure can be rolled back.

Run the install command again. It brings the newest optakt command and offers the upgrade:

curl -fsSL https://get.optakt.ai | bash

If the optakt command is already current:

sudo optakt upgrade

On a Mac, optakt upgrade, without sudo. In the admin app, the owner can also start it from Settings with u.

What an upgrade does

1. On a standard deployment it first tries the new version's database changes on your data and rolls them back. If the database cannot be reached or a change fails, it stops before replacing the service.
2. It downloads and verifies the new release.
3. It brings the service and its configuration in line with the new version, and restarts it. It tunes an Optakt-managed database; for a server you manage, it reports server-wide settings for you to apply.
4. It checks that the service answers, and ends with a list of anything you should know.

Your configuration file is kept as it was, as one.env.previous, whenever the upgrade changes it.

Upgrades follow the channel your licence allows.

If an older or nonstandard installation needs its folders repaired, that repair comes first and stops the service. A failed repair leaves it stopped at the point it reached. Read the named error and rerun the upgrade after fixing it; do not treat this as a transactional database rollback.