Appimages will run fine anywhere they are placed on the file system. When they are placed in a directory that is in the PATH
, such as /usr/local/bin
, they can be run just by typing the file name at the terminal.
There will be no side effects except for what you indicate yourself: /usr/local/bin
is a system directory, so tools to auto-update an app-image will not be able to perform the update.
Still, there is no good reason to place your appimage there, unless you rename the appimage to a simple name that conveniently can be typed from the command line. But then the version information in the file name is gone.
Better practice
Place your appimages in a dedicated directory, anywhere.
Then link the appimage to a directory that is in your path. Rename the link to an easy name:
- If you are the only one needing to run the appimage, link it into
~/.local/bin
.
- If all users should have access, place it in a system directory and link it into
/usr/local/bin
.
For example, if Joplin-2.9.17.AppImage
is in ~/.appimage
, following command will link it into /usr/local/bin
with an easier name.
sudo ln -s ~/.appimage/Joplin-2.9.17.AppImage /usr/local/bin/joplin
- Rather than typing
Joplin-2.9.17.AppImage
, you will type joplin
to start the program
- You continue to easily see which version you are running
- If you upgrade to
Joplin-2.9.18
, you can replace the symbolic link by one linking to the new version. You could keep the old appimage around a bit in case there are issues with the new version.