Skip to content

Updating

How Strawly is versioned

Strawly uses Semantic Versioning: MAJOR.MINOR.PATCH.

  • Core version. The frontend and backend are released together and always run the same version, for example 1.5.0. This is the core version.
  • Module versions. Each module, such as Azure Optimizations, has its own version and states which core versions it supports, for example >=1.5.0 <2.0.0.
  • Within one major version, upgrades are safe for modules. Changes to the database and the API only add things. A module that works with core 1.5 keeps working with core 1.9. A new major version, such as 2.0, can remove things, and modules need a release that supports it.

The list of releases and what each module supports is versions.json in the deployment repository.

Upgrade

strawly upgrade

This command:

  1. Downloads the newest release list.
  2. Picks the newest core version that every enabled module supports, and the newest module versions for it.
  3. Shows the plan and asks for confirmation.
  4. Backs up the database to the instance's backups/ folder.
  5. Downloads the new images, updates the database, and starts the new versions.
  6. Waits until Strawly reports healthy.

To move to a specific version instead of the newest:

strawly upgrade 1.6.0

Release candidates such as 1.7.0-rc.1 are skipped unless you add --pre.

What upgrade refuses

strawly upgrade does not start an upgrade that would leave a module without a supported version. Strawly also checks itself when it runs:

Situation What you see
The frontend and backend run different versions A full-page notice naming both versions
A module needs a newer core The module pauses its collectors. Administrators see a banner, and Settings > About shows the reason.
A module is too old for the core The same, with advice to upgrade the module

Roll back

If an upgrade fails or you want the previous version back:

strawly rollback

This restores the previous versions and the database backup taken right before the upgrade. Anything changed in Strawly after the upgrade is lost. Going back to an older version without restoring the database is not supported, because the upgrade may have changed the database structure.

Check versions

strawly status

Or open Settings > About in Strawly, which lists the frontend, backend, database schema and every module, with its compatibility.

Keep the strawly command current

strawly upgrade updates the release list on its own. To update the command itself:

strawly update

TrueNAS and manual installs

See Deploy on TrueNAS and Manual Install.