use proxy automatically if connection is blocked

[Boria138]

Let me give you an example: my app is mainly aimed at a CIS audience, where there are sometimes issues with GitHub, so everything is hosted on my own Gitea. But the opposite situation also exists—there are countries where all .ru domains are blocked; for them, GitHub would be the best option. I’ve set up a development mirror for them to download releases, but I have absolutely no idea how to configure auto-updates for AppImage. I’d like to teach the AppImage Updater to accept multiple URLs and switch to an alternative if one is unavailable.

[Samueru-sama]

you will have to setup a fixed url for the .zsync update.

I'm actually not sure how to do this, I know eden does it:

./eden --appimage-updateinfo
zsync|https://stable.eden-emu.dev/latest/Eden-Linux-amd64-clang-pgo.AppImage.zsync

[Samueru-sama]

also worth adding that our appimageupdate supports using a proxy.

so you can host the artifacts on GitHub and download them still even if your country is blocked

Feel free to open a request at the appimageupdate repo so that this happens automatically

[Boria138]

also worth adding that our appimageupdate supports using a proxy.

so you can host the artifacts on GitHub and download them still even if your country is blocked

Feel free to open a request at the appimageupdate repo so that this happens automatically

Unfortunately, I'm not very familiar with Rust, so for now I'll stick with

gitea-releases-zsync|git.linux_gaming.ru|Linux-Gaming|PortProtonQt|latest|*x86_64.AppImage.zsync

According to the documentation, this should work, and anyone with the .ru domain blocked should consider using a proxy; it’s possible to set Gitea as the primary source and use gh-releases-zsync|Boria138|PortProtonQt|latest|*x86_64. AppImage.zsync as a backup mirror would certainly be easier, but since you don’t have any such plans and I can’t contribute myself, let’s stick with this.

[Samueru-sama]

Unfortunately, I'm not very familiar with Rust, so for now I'll stick with

I didn't tell you to open a PR, just the feature request.

I have no problem in adding the feature, but I need testers from countries that get blocked.

[Boria138]

I didn't tell you to open a PR, just the feature request.

I have no problem in adding the feature, but I need testers from countries that get blocked.

If you need testers, that's fine.

[Samueru-sama]

@Boria138 what error do you get exactly when you attempt to use appimageupdate -Or /path/to/appimage/from/github?

[Boria138]

@Boria138 what error do you get exactly when you attempt to use appimageupdate -Or /path/to/appimage/from/github?

Since GitHub itself isn't blocked—only some of its CDN's IP addresses are—everything loads, but very slowly, sometimes at a speed close to zero.

[Samueru-sama]

🤔

@Boria138 what happens if you do this:

make a file named appimageupdatetool.toml, place it next to appimageupdatetool and add this to it:

github_api_proxy = "https://api.gh.pkgforge.dev"

Is it faster now?

[Boria138]

🤔

@Boria138 what happens if you do this:

make a file named appimageupdatetool.toml, place it next to appimageupdatetool and add this to it:

github_api_proxy = "https://api.gh.pkgforge.dev"

Is it faster now?

yes

[Samueru-sama]

Well this is gonna be complicated.

My idea was to use the proxy if connection were forbidden, but given that instead you have slow connection I don't think I can implement automatic fallback in that case.