Updating

Lastboard makes updates as painless as possible. We offer multiple ways to keep your installation current.

Web Updater

The easiest way to update is directly from the Lastboard web interface. Installing an update is restricted to the administrator — the single account created by the Setup Wizard. Members can use Lastboard normally but never see the update controls.

1. Open Settings and go to About.
2. Click Check for Updates. It asks the release server again, so the answer is always fresh (the dot in the top bar and the panel reuse one answer for ten minutes). If an update is available, Update opens the update window.
3. Confirm there, and the window follows the process step by step — download, signature, integrity, extract, install, restart — turning each step green as the server completes it. If a step fails, it turns red with the reason and the remaining ones are left untouched.

The window stays in charge until the end: it cannot be dismissed once the install starts, and the page reloads by itself as soon as the new version answers. You can close the settings panel behind it without interrupting anything.

💡 Tip: Turn on the Beta channel under Settings → About to receive the latest pre-release versions. It is a setting of your account, so it has to be on for the account you check with. Only the newest beta is kept in the repository: when a newer one comes out, the previous one is removed, and you are offered the newest.

Just published, and nothing shows up? A release’s page appears about ten minutes after its tag is pushed, while its files are built. A check made before then — by the top bar or by anyone else on your server — finds the previous version and keeps that answer for ten minutes. Press Check for Updates again a little later. An installed app that was open before you updated keeps running the old interface until you close it fully and open it again.

Running unprivileged? If you run Lastboard as a non-root user (by setting PUID/PGID), the in-app web updater is unavailable — the process cannot replace its own binary. Use the Manual Update steps below instead (docker compose pull for Docker, or re-running the install script for native installs).

Manual Update

Docker Installation

If you installed Lastboard using Docker Compose, pull the latest image and recreate the container:

docker compose pull
docker compose up -d

Native Installation

Run the native installation script again. It detects your existing installation and updates the binary while preserving your configuration.

curl -fsSL https://git.codigosh.com/CodigoSH/Lastboard/raw/branch/main/install.sh | sudo bash

It tells you which version you have and which it is about to install. If you already have the latest one it says so and changes nothing. To install it again anyway — to repair a damaged binary, or to answer the proxy question differently — add --reinstall:

curl -fsSL https://git.codigosh.com/CodigoSH/Lastboard/raw/branch/main/install.sh | sudo bash -s -- --reinstall

What Happens During an Update?

When updating natively or via the web interface:

1. The new release binary is downloaded from Forgejo.
2. Its checksum is verified against the line of the release’s checksums.txt that names that archive, and a download over the size limit is refused.
3. When release signing is enabled, checksums.txt must carry a valid signature (checksums.txt.sig) — a missing or invalid signature aborts the update, so a tampered mirror cannot serve a forged binary.
4. The existing lastboard binary is replaced. If that fails, the previous binary is put back and the update window says so. Only one update runs at a time, and each one works in a directory of its own that is removed afterwards.
5. The systemd service (or container process) automatically restarts.

See Release Signing for how the signature is produced and verified.