Skip to content

v0.1.18

Choose a tag to compare

@peppeaiello peppeaiello released this 13 Nov 16:28
· 36 commits to main since this release

If you installed Atrio before 0.1.17, run the install command once more, even after updating from the settings:
until 0.1.17, updates from the settings changed only the web UI, so the new backups, safe updates and activity log
need the services on the server to be updated once. After that, updates from the settings bring them too.

curl -fsSL https://raw.githubusercontent.com/peppeaiello/atrio/main/scripts/install.sh | sudo bash

New

  • Settings file, to move to a new machine: Settings → Settings file saves the dashboard, the push alerts, the backup folder and automatic backups, and the backup key in one file, encrypted on the server with a password you choose. Loading it on a new install puts them back; a server that already has another backup key asks before replacing it and keeps the old one. The README has a short guide to moving.
  • Unused app images, in Settings → Storage: CasaOS keeps the old image after every app update and after an uninstall, and they add up (on our test server, 16 images and about 18 GB, mostly old Immich versions). Atrio lists the images that no container, running or stopped, and no installed app uses, with their size and date, and removes them one by one or all together, showing the space freed. Nothing is removed on its own.
  • Update available for apps on "latest" too. CasaOS only offers an update when the App Store moves an app to another tag, so apps on latest, or on a tag like 3 that keeps getting new builds, never showed one. Every 6 hours the server now asks each registry (Docker Hub, GitHub, linuxserver and others) which image the app's tag points at, and the tile shows Update available when it is newer than the one running. Update now saves a backup, downloads the new image of the same tag, recreates the app and checks that it stays up. The tag never changes, and nothing updates on its own. Apps pinned to a digest, and images built on the server, are left out.
  • Ignore updates in an app's menu turns its Update available badge off, for an app you keep on its version on purpose. It can still be updated from the same menu, and Show updates again brings the badge back.
  • Activity, a tab of the notification centre (also opened from Settings → System and the command palette): what happened on the server, newest first and by day. Apps installed, removed and updated (also outside Atrio), backups by hand, automatic and before updates, restores, backup folder and schedule changes, image cleanups, settings files and Atrio's own updates, with the reason when something failed. The services on the server write it, so it is there even when nobody had Atrio open.
  • Safe updates, run by the server. Updates to the App Store's version now go through the server too, like the ones above: a backup first, then the App Store's image written in the app's compose file (only the image line of each service, and only another version of the same image), the download, the app recreated and a check that it stays up. If the new version does not start, the app goes back on its own to the backup made just before, compose file and data, also with no browser open, and the tile says so. A failed download leaves the app as it was.
  • While an app updates, its tile shows each step on its ring (backup, download, start, check) instead of the menu staying open with a loading animation.

Fixed

  • The install command run with ATRIO_SOURCE, to try the services of a checkout, kept the services of the release instead.

Full changelog: v0.1.17...v0.1.18