PORTABLE LINUX APPS

The "Install" button on each app page uses the pla-install:// protocol. You need a helper application to handle it.

Install AppGallery to register the protocol handler and enable one-click installation.

Alternatively, install apps manually via AM on the command line.

Portable Linux Apps are standalone applications for GNU/Linux that can (theoretically) run everywhere, also on a USB stick. These applications can be AppImage packages (see appimage.org) or standalone archives (for example Firefox, Thunderbird...).

This catalog aims to survey and list all the AppImages and autonomous programs, and aims to provide a centralized point where you can document yourself on individual apps and where you can easily reach the URLs to the sources, both through the pages dedicated to each app and by reading the "installation scripts".

Yeah, each app has its own installation script, PKGBUILD style, but with an alternative package manager named "AM", which works like the more classic APT, PacMan/YAY, DNF... and which can therefore place them in specific paths of the filesystem , like any program, and allows updates via a system of scripts called "AM-updater". If an app can't update itself, the dedicated "AM-updater" script will use an application-specific method to always update your favorite apps to the latest version. FOR REAL!

This catalog is open source. You can edit its pages, update them and see the sources clearly, as a "wiki".

About other catalogs

While I recognize the role they have had so far in supporting the diffusion of AppImage as a packaging format, through the years, as a former user, I would like to underline what led me to open an alternative catalogue:

• "appimage.github.io" serves more than anything else to catalog the AppImages based on validation processes based on Github Actions (i.e. that the package is compatible with old versions of Ubuntu LTS). From the developer's point of view it's fine, but from the point of view of the user who searches for AppImage packages without going into the depths of the internet, it's totally useless. As a catalog it is limited to showing only that an app exists or has existed in the past, without worrying about obsolete packages that no longer exist, but still listed only "to make up the numbers". Many pages have no buttons to the sources and all pages have no additional information on individual apps, each page is simply a copy/paste message that says that the app "is available as an AppImage which means one app = one file..." etcetera etcetera.
• "appimagehub.com" hosts applications not always provided by the original developer, just check the profile of whoever uploaded the application and how many "products" they uploaded. Some admit that they are not the developers, despite having a donation button available, effectively leading them to earning on work of others, and are often greedy enough to not include the real source! These profiles use random hosting services for these applications, and Pling's APIs does not allow you to clearly verify the origin of any package that is downloaded. There is no control over this, and the only validity check of a "product" is the feedback of the users who use it, and which in any case is not sufficient either to guarantee the safety of an app, nor to do justice to the real owner of that package, who was in fact "robbed" of its work.

Furthermore, none of them track updates consistently.

From the aforementioned defects I understood what a catalog of portable applications should NOT do to be reliable.

All app data is stored as JSON files sourced from the AM application list. Each app has a corresponding file in the apps/ folder with its description, sites, sources and screenshots, generated by the pla-site-tool.

• app icons must be 128x128 PNG files placed in the icons/ folder, named after the app;
• the application lists are automatically generated by this script. Any changes to the lists and descriptions must be made to this file, which is the general list of apps managed by "AM"/"AppMan";

For any suggestions, open an issue at https://github.com/ivan-hc/AM or a pull request at https://github.com/Portable-Linux-Apps/Portable-Linux-Apps.github.io

If you want to improve an app's page in this catalogue (i.e. add more detailed description, screenshots, sites, etc.), read on.

The app files in apps folder are in a simple markdown-ish format, the description must be wrapped between the === lines.

1. Create a text file like this:

   # some app
   
   ===
   description of your app. must be within the `===` lines.
   only use **bold**, *italic*, ++underline++, lists markdown here
   - do not add links or images here
   - use SOURCES field if you package someone else's app
   ===
   
   # SCREENSHOTS: https://Portable-Linux-Apps.github.io/contribute_ss.webp
   # SITES: https://someapp.io
   # SOURCES: https://github.com/name/someapp-appimage
   # BUTTONS: Label_of_Button::https://discord.gg Donation_Link::https://someapp.io/donate
   

   Explanation of the fields:

   • SCREENSHOTS: a space separated list of image URLs
   • SITES: space separated site URLs that provide the AppImage
   • SOURCES: if you are packaging someone's else's app, link the git repo(s) here
   • BUTTONS: space separated button definitions in the form of Button_Title::URL
2. Copy the app's icon (should be of same name) to icons folder.

Depends on what you mean by "centralized package repository", if you mean a repository that stores them all like Debian-based distributions do with DEB packages, no, there are thousands of packages, and they are usually distributed to remote sites and difficult to find.

If instead you mean an AUR-style repo with scripts that easily find all AppImages, you're in the right place!

This catalog and its CLI, "AM", make it easy for you to find, install, integrate and update all AppImage packages!

This catalog is just the frontend for an ever growing database that aims to extend not only to x86_64 architecture apps listed here, but also to all others, from the modern ARM64/aarch64 to oldest i686, as an universal solution for all AppImages and portable programs for GNU/Linux!

Check the wiki for guides and documentation.

If you still need help, open an issue on GitHub.

You can also join the pkgforge Discord to ask the community directly.

NOTE, the installer scripts in the "INSTALLER" column are intended for use via "AM", and are therefore dedicated to a system-wide installation of applications (in /opt), and all that "AppMan" does is convert those scripts for local installation, changing the paths. They are listed here for reading purposes only!

Should you decide to run them manually, the only way to remove the application is to run the command "sudo /opt/appname/remove", where "appname" is the name of the application directory containing the "remove" script. Likewise, you can also update applications by running the "AM-updater" script in the same directory.

The "AM" project allow the autonomy of installed apps, regardless of the presence of "AM" itself in the system. However, it is strongly recommended to use "AM" and "AppMan" to take full advantage of all the benefits you could get from an application installed in this way.

If you are here just to download apps manually, click on the program name and check the URL(s) on the application page. This site does not provide direct links, for security reasons, but it does provide the exact sources and references where you can find them!

Transparency and credibility are the focus of this catalog. Happy exploring!