Updates
How Basalt Host keeps itself up to date, how the apps update, and how to update by hand.
Basalt Host
Basalt Host keeps itself up to date. A minute after it starts, and then twice a day, it looks for a new version. When there is one, and Update automatically is on, it waits until nothing is playing or copying, installs it, and restarts. Your devices reconnect by themselves.
How the new version goes in depends on how the host was installed:
| Host | How it updates |
|---|---|
| Windows | Basalt Host closes, updates and opens again by itself |
| Linux desktop, .deb or .rpm | A small system helper installs the new package. You are not asked for a password |
| Linux desktop, AppImage | The AppImage file is replaced with the new one, where it is |
| No screen | The host asks a small system service, basalt-host-update, which installs the new package |
| Docker | Never by itself. Pull the new image: see below |
Update now
- In Basalt Host: in its settings, under the version, choose Check for updates, then update when it finds one.
- From any device that manages the host: in Manage host, under Updates.
- On a host with no screen:
sudo basalt-host update.
Turn automatic updates off
Turn off Update automatically, in Basalt Host’s settings or under Updates in Manage host. The host still looks for new versions and says when one is out, and you install it when you choose.
In Docker
A container never changes itself. When a new version is out, Manage host and basalt-host status say so. Then, in the folder with your compose.yaml:
docker compose pull && docker compose up -dWith docker run, pull the new image, remove the container, and run it again with the same settings. Everything in /config carries over.
The apps
Basalt on Windows and Android looks for new versions by itself. When one is out, it shows what is new in it, and installs it when you choose to: on Android, under More.
- On Windows, the update installs in place, keeping your pairing and settings.
- On Android, Basalt downloads the update and hands it to Android’s own installer. The first time, Android asks you to allow Basalt to install it.
Update the host first, then your other devices. A device on an older version keeps working with a newer host.
Always the official release
Every update, for the host and the apps alike, is the newest release published on Basalt’s GitHub page. It is checked against its published SHA-256 checksum before it is installed, and a download that doesn’t match is thrown away.
A device that manages the host can ask it to update, but never choose what is installed. On Linux, the system helper that installs host updates only ever installs the newest official package, whatever asked for it.
Something unclear, or not covered here? Ask in Help and setup, where the community and Refora Technologies answer, or write to us, and we will improve this page.