Upgrades and verifying downloads
YARMA is released as numbered versions (1.2.3; pre-releases look like 0.1.0-alpha.4). The
current version and its files are on the download page;
these docs always describe that version (shown in the menu).
What a release contains
| File | Use |
|---|---|
yarma-server-native-X.Y.Z-linux-amd64.tar.gz |
complete server for Ubuntu 24.04 without Docker, including the agent packages (install) |
yarma-single-host-X.Y.Z.tar.gz |
Docker Compose bundle for one server (install) |
yarma-X.Y.Z.tgz |
Helm chart for Kubernetes (install) |
yarma-server-X.Y.Z-linux-{amd64,arm64}.tar.gz |
server programs only |
yarma-agent… .msi, .pkg, .deb, .rpm |
agents for Windows (x64), macOS (Intel and Apple silicon) and Linux (x86_64 and 64-bit ARM) (agents) |
SHA256SUMS |
checksums of every file |
Container images are published as registry.avadeja.com/yarma/yarma-api, yarma-web and
yarma-license-center, tagged with the version. Pulling needs no account.
Verify a download
V=<version>
curl -fLO https://yarma.avadeja.com/downloads/$V/SHA256SUMS
sha256sum --ignore-missing -c SHA256SUMS # macOS: shasum -a 256 -c SHA256SUMS
Every file you downloaded must show OK. Agents installed with the console's one-line
command are checked automatically against the checksums your server publishes.
Pre-release packages are not code-signed yet: Windows SmartScreen and macOS Gatekeeper ask for confirmation. Signed packages come with the 1.0 release.
Upgrade the server
Take a backup first, read the release notes, then:
| Installation | Upgrade |
|---|---|
| Ubuntu (native) | download the new bundle, unpack it and run sudo ./install.sh again (no options needed); settings, keys and data are kept and database changes run automatically |
| Docker Compose | set YARMA_VERSION in .env to the new version, then docker compose pull && docker compose up -d (details) |
| Kubernetes | helm upgrade with the new chart version (details) |
Upgrade the server before the agents. Versions are not skipped backwards: downgrading a server after its database was upgraded is not supported; restore the backup instead.
Upgrade agents
Run the one-line install command from Settings → Enrollment again on a device (no token is needed on an enrolled device), deploy it with your management tool, or install the new package over the old one. Devices keep their identity and configuration.
Documentation for Yarma 0.1.0-alpha.5. Something unclear? .