Updates
Leyla can keep itself up to date. A new release is fetched, tried against your own library and players before it may run, and installed when nobody is watching. This page says what the server does, what it never does, and how to choose.
Choose how updates arrive
The setup asks once: Keep Leyla up to date?
- Yes
- Releases install on their own, at a quiet moment.
- No
- Each new release is shown in Administration › This server › Updates and waits for you.
The same page changes the answer later, and chooses the channel:
- Stable
- Every server. A release reaches it after it has run on canary.
- Canary
- The servers that take a release first: Leyla’s own, the demo, and testers who opt in.
A release that fixes a security flaw goes to both channels at once. Both settings apply after a restart, as the page’s restart bar says.
A plan is needed New versions come with an active plan or a running trial, and every server has one until the open beta ends on December 31, 2026. Without one the server keeps running the version it has, and nothing is fetched. After twelve paid months that version is yours to keep. See Pricing.
Note A newer image or package always wins. If you update the container image or install a newer .deb, .rpm or Windows installer yourself, that is the version that runs.
What happens to a new release
It is fetched
Once a day the server looks for a newer signed list of releases: a plain download of
index.jsonfrompacks.leyla.media. Nothing about the server is sent, not even its version.A release lists every file it is made of, for each platform, with its size and SHA-256. Only the files the server does not already hold are downloaded, and each is checked before it is kept. A release that left ffmpeg alone costs about 20 MB.
It is rehearsed
Before it may run, the new release answers what this server’s library and players asked of the one running now. Every file in the catalogue is identified again, and every distinct thing the playback planner was asked in the last 30 days is planned again. This happens in a sandbox with no network, no database and none of the server’s own files, and takes seconds.
A file that would lose its match or its title, or a play that would convert more than it does now, holds the release. It never runs here, and Administration › This server › Updates lists what it found.
It is installed at a quiet moment
With nothing worse, the release waits until nobody is watching: every stream paused for longer than the server takes to restart, and for at least two minutes. Then the server restarts into it. Update now on the page does the same at once.
It starts
At every start, the installed program runs the newest fetched release that is newer than itself and whose every file still matches the signed list. A release that was withdrawn is never run, and one that starts three times without coming up is set aside for the installed program.
What it never does
- It never changes the database without a backup first. A release that changes the database is installed after a backup, and its changes go in together or not at all. A release that cannot make them holds itself, and the installed program starts again on the database as it was.
- It never runs files that do not match the signed list, and never a release older than the program that starts it.
- On Windows it never writes to
Program Files. The service stays the program the installer put there and runs the newer release from%ProgramData%\Leyla\bin\<version>\. Stopping the service stops the release.
Where things are
| What | Where |
|---|---|
| The choice and the channel | Administration › This server › Updates |
| Releases fetched | <data>/bin/<version>/, with rehearsal.json beside each |
| A held release | <data>/bin/<version>/.held |
| The signed list | <data>/packs/index.json and its signature |
What’s new has the latest release’s notes.
Something missing or wrong here? Tell us.