Squorli Server 0.6.0
Squorli Server now also runs on Windows without Docker, as a package with its own setup. For installations with Docker little changes: the app server's Compose service has a new name.
Before you update
- Nothing to do for the database: no migration, and no new variable you have to set.
squorli backup, thensquorli updateis enough. - The app server's Compose service is named
servernow (appbefore).squorli updatealone leaves your installation as it is, with the old name. To take the new name over, run the install script again and choose "Update": it fetches the new deploy files and replaces the container; database, files and secrets stay. From then on it issquorli logs serverandsquorli restart server;appis still understood. - Installed by hand: download
compose.ymland the overlays you use again and start with--remove-orphans. An overlay or a Portainer stack of your own that saysservices: app:has to sayserver:. A reverse proxy that points toapp:3000keeps working: the container still answers to that name in its network. - Two new variables, both for installations without Docker only:
LISTEN_HOSTandDOCTOR_TOKEN. The package for Windows sets them itself. Leave both unset with Docker Compose. - No new desktop app and no newer Squorli Directory are needed.
New
- Windows without Docker. A package for Windows 10 (from 22H2), Windows 11 and Windows Server 2019, 2022 and 2025 (64 bit): the app server with its own Node.js, PostgreSQL, LiveKit and Caddy, set up as Windows services that start with the machine. Its setup asks the same questions as the install script for Linux, in German or English, and the same command manages it afterwards:
squorli status,logs,backup,restore,update,doctor.squorli restorealso takes the backup of a Linux installation, which is how a server moves from Linux to Windows. The package is attached to this release assquorli-server-0.6.0-windows-x64.zipwith a.sha256file; the guide is at https://squorli.com/en/docs/install/#windows. - What was run on Windows, and what was not yet: installed and run on Windows 11 with a reverse proxy on the same machine and on localhost: setup, services, voice, a restart of the machine, backup and restore, update and removal. The package's automatic test (setup, every command, backup and restore, update, removal) also passes on Windows Server. Still to come: the bundled Caddy with a real certificate, IIS in front (a template is included), Windows 10, and a Windows Server with people on it. The programs in the package are not signed, so Windows may ask before it runs them.
Improved
- The server stops at once. Stopping or restarting the container took ten seconds, because the server did not react to the request to end; now it closes its connections and ends in under a second. Updates and restarts are that much shorter.
- A tidy log. Every start wrote two notices of the database as several lines of plain text between the log's lines. They are gone at the default log level.
Image: ghcr.io/danielklessa/squorli-server:v0.6.0 (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.0 in .env, then docker compose pull and up -d. Windows without Docker: the package squorli-server-0.6.0-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/