Updates & releases¶
All four projects follow the same release convention. That allows NestrisLTM to find, verify and install updates for the whole setup from one place.
Release convention¶
- Tags use
v<semver>, for examplev1.2.0. Pre-releases look likev1.3.0-rc1. The tag must match the version in the project file, or the release workflow refuses it. - GitHub Actions builds every release from source. No release is built on a developer machine.
- Each release has a
SHA256SUMS.txtlisting every asset, signed with Ed25519 (SHA256SUMS.txt.sig). The apps accept an update only if the signature matches a public key built into them.
flowchart LR
TAG["<span style='color:#ffffff'>git tag v1.2.0</span>"]:::ext --> CI["<span style='color:#ffffff'>GitHub Actions<br/>build + test</span>"]:::ext
CI --> ART["<span style='color:#ffffff'>Assets<br/>.exe · .zip · .deb · .bin</span>"]:::ext
ART --> SUM["<span style='color:#ffffff'>SHA256SUMS.txt</span>"]:::ext
SUM --> SIG["<span style='color:#ffffff'>Ed25519 signature<br/>SHA256SUMS.txt.sig</span>"]:::ext
SIG --> REL["<span style='color:#111111'>GitHub Release</span>"]:::ltm
classDef ltm fill:#f5b800,stroke:#7a5c00,color:#111,stroke-width:2px
classDef ext fill:#64748b,stroke:#334155,color:#fff,stroke-width:2px
NestrisLTM update manager¶
NestrisLTM checks GitHub Releases one minute after start and then every 24 hours, or when you click Jetzt prüfen. No internet at the venue is normal: the check fails quietly and the UI shows when it last succeeded.
Installing always takes a click. Nothing updates by itself, and never silently in the middle of an event.
sequenceDiagram
autonumber
participant L as NestrisLTM
participant G as GitHub Releases
actor A as Admin
participant DB as PostgreSQL
L->>G: check releases (stable / beta channel)
G-->>L: v1.2.0 available
L-->>A: tray balloon "Update verfügbar" + admin page
A->>L: Installieren
alt games are live or a round is running
L-->>A: "Turnier läuft – trotzdem aktualisieren?"
end
L->>G: download installer + SHA256SUMS.txt(.sig)
L->>L: verify Ed25519 signature, then SHA-256
L->>DB: pg_dump backup → backups\ (last 10 kept)
L->>L: run installer silently (/update=1) and quit
Note over L: installer restarts NestrisLTM on the new version
| Setting | Meaning |
|---|---|
[updates] enabled |
Automatic checks on/off |
[updates] channel |
stable (releases only) or beta (also pre-releases) |
[updates] owner / repo |
GitHub source, useful for forks |
[updates] check_interval_h |
Check interval, default 24 |
Rollback. Andere Version … lists recent releases. A downgrade across a database migration requires restoring the backup taken before that update, and the admin page explains this.
Roadmap for the other components¶
| Component | How it is updated today | Planned |
|---|---|---|
| NestrisLTM | One-click update manager (above) | — |
| nestris-terminal | Run the new installer (no admin rights needed) | Planned Update tab in the hidden admin menu |
| nestris-station | sudo apt install ./nestris-station_<v>-1_<arch>.deb |
Planned "Station aktualisieren" from the NestrisLTM stations page |
| RFID reader | Flash with esptool or PlatformIO |
Planned Flash from the terminal or station it is plugged into |