AppImage "integration"?

[whoami]

Wow, what a thread

Curl-proxy / wget-proxy scripts in Templates so users can add GPG distro keys linked to added external repositories

Updates Edit: Extended PoC of this idea is here. This is the blocking version (where non-networked TemplateVM will not translate curl/wget to curl-proxy/wget-proxy in the wrapper scripts. Edit2: PoC code download here Edit3: A non-blocking example for curl-wrapper automatically translates curl calls to curl-proxy calls under this post. Edit4: No go. MOTD is a better approach. Proxy with static port is now considered risky by thread participants. @deeplow @unman I created issue Deploy curl-…

@Insurgo

In the past I had these issues to install Signal. My solution (as low skill terminal user) was a standalone AppVM which I personally don’t like - one template for one app.

To avoid standalone AppVM I prefer standard AppVM with AppImages (if they are available). For this approach I would like to have a more integrated and user friendly approach in Qubes OS.

1. Download AppImage (in any AppVM)
2. Right-click on *.appimage than create AppImage AppVM (based on a minimal / “medium” template with network on) and create a new folder “AppImage” in home directory. Somehow the same routine like ‘copy to other AppVM’ and ‘open in disposable AppVM’. Afterwards copy *.appimage into this new folder.
3. Add this AppImageVM to the AppImage menu (see proposal above).

Advantage:

Simple: Two-clicks software installation. (Beside the permission to launch the appimage) no terminal command required. Easy to maintain / update.

secure: App is isolated in its own AppImageVM. Possible to set individual firewall settings.