AppImage Configuration
Setting Updates
Section titled “Setting Updates”Shelly supports updating AppImages in two ways:
- A static URL
- A Repository from GitHub, GitLab, Codeberg, or Forejo.
Static URL:
Section titled “Static URL:”Enter the URL to the AppImage which you have been downloaded. Shelly will use this to check for updates.
Repository:
Section titled “Repository:”You will need the Repo Owner and Repo Name. Shelly will then check for updates from this repository.
For example, if we were to add OSU as an AppImage from GitHub, the repo url would be: https://github.com/ppy/osu
We would then enter
ppy/ous in the repo url field.
Then Shelly will check for updates from the ppy/osu repository user the most recent release or from the most release pre-release based on your settings.
Key Details for updates:
Section titled “Key Details for updates:”- Shelly will check the version from the
.desktopfile and compare it to the latest release. - If the version is
Unknown shellywill update to the latest release, and track the version via the tags for the future. - If your AppImage has a self-update feature, this is the best way to update and track updates. You can use the sync feature to keep your AppImage info up to date.
Syncing AppImages
Section titled “Syncing AppImages”- Sometimes you may want to sync your AppImages with the latest release this is most useful for self-updating AppImages.
Migrating from Shelly v1 AppImage Support to Shelly v2 AppImage Support
Section titled “Migrating from Shelly v1 AppImage Support to Shelly v2 AppImage Support”- Run
shelly appimage migrate-manageror - The UI will prompt you to migrate your AppImages.