Bulk Renamer
59 lines
2.7 KiB
Markdown
59 lines
2.7 KiB
Markdown
# Using HSRename with Gear Lever
|
||
|
||
[Gear Lever](https://github.com/mijorus/gearlever) can manage and update the HSRename AppImage. Because releases are hosted on **Gitea** (not GitHub), use one of the options below.
|
||
|
||
## Option 1: Custom update URL (recommended to try first)
|
||
|
||
Gitea uses the same release path style as GitHub:
|
||
`/owner/repo/releases/download/{tag}/{filename}`
|
||
|
||
1. Open **Gear Lever** and add the HSRename AppImage (drag & drop or **Add**).
|
||
2. Select the HSRename entry and open **Update** / **Custom update URL** (or the equivalent in your Gear Lever version).
|
||
3. Try this URL pattern (with a wildcard for the tag):
|
||
```
|
||
http://brassnet.ddns.net:33983/Dawnsorrow/HS-Rename/releases/download/*/HSRename.AppImage
|
||
```
|
||
4. If Gear Lever accepts it (e.g. field turns green or validates), it may use the Gitea releases page to resolve the latest tag and offer updates when you push new releases.
|
||
5. Use **Check for updates** / **List updates** to see if it detects new versions.
|
||
|
||
If your Gear Lever only supports GitHub-style URLs and rejects this, use Option 2.
|
||
|
||
## Option 2: Static URL (manual update link)
|
||
|
||
If the wildcard URL does not work:
|
||
|
||
1. In Gear Lever, add HSRename and set **Update** to **Static URL**.
|
||
2. Paste the **direct download URL** of the current release, for example:
|
||
- **v1.0.1:**
|
||
`http://brassnet.ddns.net:33983/Dawnsorrow/HS-Rename/releases/download/v1.0.1/HSRename.AppImage`
|
||
3. When a new version is released (e.g. v1.0.2), open the [releases page](http://brassnet.ddns.net:33983/Dawnsorrow/HS-Rename/releases), open the new release, right‑click **HSRename.AppImage** → **Copy link address**, then in Gear Lever set the Static URL to that new link and run **Update**.
|
||
|
||
So: Gear Lever will only “see” updates if you change the Static URL to the new release’s download link when you want to update.
|
||
|
||
## Option 3: CLI (if you use Gear Lever from the terminal)
|
||
|
||
After adding the AppImage in Gear Lever, you can set the update URL from the command line:
|
||
|
||
```bash
|
||
# Set custom update URL (try the wildcard pattern)
|
||
gearlever --set-update-url /path/to/HSRename.AppImage "http://brassnet.ddns.net:33983/Dawnsorrow/HS-Rename/releases/download/*/HSRename.AppImage"
|
||
|
||
# Check for updates
|
||
gearlever --list-updates
|
||
|
||
# Apply update
|
||
gearlever --update /path/to/HSRename.AppImage
|
||
```
|
||
|
||
Replace `/path/to/HSRename.AppImage` with the actual path where Gear Lever stores the AppImage.
|
||
|
||
## Release download URL pattern
|
||
|
||
For any release tag `vX.Y.Z`, the direct download URL is:
|
||
|
||
```
|
||
http://brassnet.ddns.net:33983/Dawnsorrow/HS-Rename/releases/download/vX.Y.Z/HSRename.AppImage
|
||
```
|
||
|
||
So when we push a new release (e.g. v1.0.2), that new tag’s URL is what Gear Lever needs (either via the wildcard in Option 1 or by pasting the new URL in Option 2).
|