Skip to content

Squorli Server 0.6.1

Choose a tag to compare

View all tags
@github-actions github-actions released this 28 Sep 19:56
· 13 commits to main since this release
v0.6.1
7673af1

Squorli Server can keep itself up to date now, and an update stops only what it has to.

Before you update

  • Nothing to do by hand: no migration, no new variable, no file to fetch. Installations with automatic updates will take versions like this one by themselves.
  • Linux, installed with the install script: the new commands belong to the squorli command the script writes. squorli update brings the new image only; to get the commands, run the install script again and choose "Update".
  • Windows: squorli update brings everything.
  • No new desktop app and no newer Squorli Directory are needed.

New

  • Automatic updates. squorli autoupdate on sets up a job that looks for a new version and installs it. It asks how often, from every hour to once a day; with 24 hours it runs at 04:17. When nothing is new, nothing is stopped or started. Every update makes a backup first. squorli autoupdate shows the state and the last runs, squorli autoupdate off removes the job. Read the warning the command shows before you answer: an update restarts the app server whenever a version appears.
  • A version that needs you waits for you. When a version asks for work by hand before the update, the job does not install it. It notes the version in its log and waits for your squorli update, which names the release notes and asks whether that work is done.
  • The image tag stable. ghcr.io/danielklessa/squorli-server:stable always names the newest published version. latest, which the install script enters, changes with every change in development, between two versions too. squorli autoupdate on offers to set APP_IMAGE to stable, so that the job installs published versions only; a fixed version in APP_IMAGE never changes by itself.
  • Only look. squorli update --check (on Windows also -Check) tells whether there is something new and changes nothing that runs; its exit code is 10 when there is, 0 when not.

Improved

  • An update on Windows stops only what changed. When a new version brings a new Squorli but the same PostgreSQL and LiveKit, these two keep running and only the app server restarts. Until now every update stopped all services.
  • squorli update on Linux backs up first, as on Windows, and says which services get a new image; the containers whose image stayed the same keep running. A backup that fails stops the update; --no-backup leaves it out.
  • squorli backup on Linux leaves no half backup behind when it fails, and says so.

Image: ghcr.io/danielklessa/squorli-server:v0.6.1 (also :latest). Update an installation made with the install script: squorli backup, then squorli update; with Compose by hand: set APP_IMAGE=ghcr.io/danielklessa/squorli-server:v0.6.1 in .env, then docker compose pull and up -d. Windows without Docker: the package squorli-server-0.6.1-windows-x64.zip below, with its .sha256 file; update an installation with squorli update in a window opened as administrator (it backs up first). Database migrations run by themselves at the start and cannot be undone: back up first. Guide: https://squorli.com/en/docs/install/

Assets 4
Loading