Updates
Being notified
Section titled “Being notified”Élise checks for a new release at startup, every six hours and when the Settings page opens. A new release is shown with a badge. It is never installed without confirmation.
Install
Section titled “Install”From Settings → General → Élise OS updates, or over SSH:
elise updateWhat happens
Section titled “What happens”- The release is downloaded and its Sigstore signature verified.
- The previous release is kept, along with a copy of the database.
- The new containers start.
- Élise checks the health of the caregiver space and the API.
If startup or the health check fails, the current link, the configuration file, the database and the containers return to the previous release.
Docker Compose
Section titled “Docker Compose”A Docker Compose installation has no update agent: repeat the installation with the new release, after a backup.
Private fork
Section titled “Private fork”Official releases are public and need no account. For a private repository, create a read-only GitHub bot account and a classic token with repo and read:packages, then provide it:
-
on the Preparing Élise page at first boot;
-
or in an
elise-github-auth.txtfile on the boot partition, right after writing the card:username=elise-os-bottoken=ghp_… -
or in Settings → General on an installation that is already running.
The token is moved to /etc/elise/github-auth (root:root, 0600). It is never stored in the Élise database or included in a published image.
