Skip to content

Updates

Stackmill checks for a new version a minute after it starts, then once a day. Nothing is ever installed on its own: an update is a decision, and on a production cell it is a decision with a date.

The check never blocks anything. A machine with no internet keeps working exactly as before; it simply never announces a new version.

Where it appears

Next to the licence badge, and in Help ▸ Stackmill ©. Both are visible in admin or developer sessions only — an operator running a cell is not shown an update. Opening the badge gives the version, its date and its release notes. Help ▸ Update… opens the same dialog at any time.

Installing on the desktop application

The dialog installs it: the download is verified against Apemill's signature, the application restarts on the new version. The button is disabled while a cell is running — stop the cell first.

Installing on a server

  • A server with the host service (installed from the ISO or with install.sh) — click Update now. The server restarts and everyone connected is cut off for about a minute; the dialog shows the progress, the page reconnects, and the result appears as a notification. It refuses while a cell is running, verifies the image signature, and returns to the previous version by itself if the new one does not start.

  • A server without it — the dialog shows the command to run on the machine, with the same guards:

    sudo stackmillctl update

    Without stackmillctl, set the new tag in docker-compose.yml and run docker compose pull && docker compose up -d.

  • In a browser, against a desktop machine — the dialog gives the download link; install it on that machine.

Installing a given version

The dialog takes a version number, betas included. On a server, Update to installs exactly that one, with the same guards; without the host service: sudo stackmillctl update --to <version>. On a desktop, it downloads that version's installer. An older version is flagged: a file saved by a newer version is not guaranteed to work with it.

Skipping several versions

Some versions cannot be reached in one jump, because the project file format changed on the way. Stackmill then names the version to install first. Install that one, then the newest.

Projects, licence and settings are never touched by an update. On a server they live in /data, which the update does not replace.