Lorenzo Paderi

Guide: the update manager in Gear Lever

· Lorenzo Paderi

Since version 2.0.0, Gear Lever can manage updates for your AppImages.

If the app developer did not include update informations, users can add an update url where to fetch from. Here is how it works:

When the app developer includes update info

Gearlever You can preview the embedded details

You can preview the embedded details.

The data provided by the developer will be used to update the app.

When the app developer DOES NOT include update info

You can add a custom URL where to fetch updates from.

Gear Lever supports:

  • a static url (when the download link is always the same, like https://example.com/latest.appimage)
  • Github releases (please read below)

How to use a static URL

Select “Static URL” as source and simply paste the url. Gear Lever will perform some checks and the textbox will get green if the provided url meets the requirements.

How to use Github Releases

Please, follow these steps:

  • Set Github as source
  • Open the Github page of the app
  • Go to “Releases”
  • From the assets list, copy the url of latest appimage for your system and architecture
  • Identify the naming pattern and use globes (*) to mark any variables in the name

This is how a Github link is formatted:

https://github.com/user/repo/releases/download/tag_name/file_name.appimage

You should just replace the name from the file_name and tag_name.

Let’s take Audacity and Osu as examples:

Audacity

https://github.com/audacity/audacity/releases/download/Audacity-3.5.1/audacity-linux-3.5.1-x64.AppImage

this url should be pasted as:

https://github.com/audacity/audacity/releases/download/*/audacity-linux-*-x64.AppImage

Osu

https://github.com/ppy/osu/releases/download/2024.625.2/osu.AppImage

becomes:

https://github.com/ppy/osu/releases/download/*/osu.AppImage

Osu does not require any globe (*) in the file_name, because the name is always the same.