PrintSpool VS AppImageLauncher

I'm excited to try these things for 3D printing - sure some might say "Octoprint couldn't run on that! It can't even handle the the Pi Zero!" And they'd be right, except if say someone just happened to be rewriting Octoprint in Rust for this exact reason.

It's a fairly simple check atm. Here's what it looks like in my code: https://github.com/tegapp/teg/blob/develop/crates/server/src/server_query.rs#L21

Every file that you want to execute has to be in your environment PATH. I would also advise to put symlinks and personal executables in ~/.local/bin and put that to your path. Since your user has ownership over that directory, you won't have any probs with permissions that may or may not occur at all. Since we're talking about AppImage files, you might also want to take a look at AppImageLauncher which does a pretty good job at creating entries for your Desktop Menu for the AppImage files that you install to your system.

I think it's safe to install it directly as it stores everything in a single directory. For AppImages there is also AppImagePool + AppImageLauncher (can be installed rootless, useful for better integration of appimages).

This reminds me of a prettier version of AppImageLauncher. Is there also an "Uninstall" option in the right-click menu of the app launcher?

I'm using AppImageLauncher on Fedora.

"... I recall that this was related to an issue with most Electron apps, wherein the AppImage cannot be integrated with the desktop or the favourites bar. So far we've found that the AppImageLauncher (https://github.com/TheAssassin/AppImageLauncher) helps with getting around this!