AppImageLauncher
Our great sponsors
AppImageLauncher | com.bitwarden.desktop | |
---|---|---|
183 | 15 | |
4,909 | 13 | |
- | - | |
3.7 | 7.3 | |
7 days ago | 17 days ago | |
C++ | ||
MIT License | - |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
AppImageLauncher
- New to fedora, any advices?
- Flatpak Is Not the Future
-
What is the proper way to install?
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.
-
What’s the best way to install App Man, direct or via distrobox?
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).
- Newer Linux Administrator, have a question regarding Debian builds like Ubuntu and installer.appimage files.
- AppImage won't ask anymore to Integrate after Running only once
- AppImageLauncher no longer working on Fedora 38
-
Working on an app to "install" and manage 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?
-
Can I trust Flatpak apps if they are not managed by the app developer?
I'm using AppImageLauncher on Fedora.
-
Standard Notes users - how are you creating shortcut to SN inDock?
"... 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!
com.bitwarden.desktop
-
Flathub – The Linux App Store
> One thing I don't know about (which maybe somebody can inform me/us about): the wiki states that PRs are reviewed by Flathub reviewers, but I see no sign of human review on e.g. https://github.com/flathub/com.bitwarden.desktop/pull/167 (or others in that repo). What's the actual process?
In this case, I think the lack of human involvement is mostly a good thing. Flathub was criticised for having outdated packages[1]. Using automation to automatically update packages is mostly a good thing.
Obviously, we want to see thorough review of new packages, but that's a separate issue.
[1] I thought I read this in an LWN article, but I can't find it. But see e.g. https://github.com/flathub/org.qutebrowser.qutebrowser/issue...
-
Can I trust Flatpak apps if they are not managed by the app developer?
for example, bitwarden's flatpak on github shows basically just repackages the official debian build into a flatpak build. in this case i think it's pretty safe (in fact i use the flatpak).
-
Bitwarden not working
You might also be interested in learning a little about Flatpaks and downloading/installing programs from Flathub. I'll give you the basic background: It's an alternative (in some ways, honestly, modern) way of installing programs that can be sandboxed/permissioned. It's a way of releasing software that also helps ensure compatibility across a wide variety of systems. It's also a way of releasing software that can update independently from the base installation. You can think of it sort of like an app store on a phone where the programs are a bit self-contained and can update independently from the phone's operating system. https://flathub.org/apps/details/com.bitwarden.desktop
- First config install
-
In using Ubuntu for ARM, I noticed there's a 4-year-old version of Bitwarden ARM64 on the Ubuntu Software Center. Be cool if you updated it, but maybe remove it at this point. It’s identified as unsafe due to ‘using a legacy windowing system’, and while it installs, the login errors out.
See https://github.com/flathub/com.bitwarden.desktop/issues/63
-
Publishing Electron apps to flathub
Example of an application but with Electron: https://github.com/flathub/com.bitwarden.desktop
-
I'm a very basic user. What am I missing?
Since we're on the subject, you can also host your own BitWarden if you wanted. Bitwarden also has a desktop client for Linux as well. Alternatively if enabled 3rd Party Repositories or just manually enabled Flathub, you can install the Bitwarden flatpak.
- I made a BASH script that removes Snap from an Ubuntu system and replaces it with Flatpak.
-
Vote for the Bitwarden flatpak app to become official
It's not really that much of a risk. If you look at the yaml file you can see exactly what permissions it requests and what happens when the package is built.
-
What's the current obstacle to more developers directly pushing their apps to flathub?
Luckily, Flathub is transparent in what manifests are used in the production of the Flatpaks they host. For example, this is the one for Bitwarden. You can take some time to learn how Flatpaks are built, but this one seems pretty straight forward. They are taking the .deb file from Bitwarden's github release page and extracting the executable from there. Then it adds a couple extra files, which are viewable within the manifest file, to make it into a Flatpak app.
What are some alternatives?
appimaged - appimaged is a daemon that monitors the system and integrates AppImages.
desktop - The desktop vault (Windows, macOS, & Linux).
void-packages - The Void source packages collection
snapd - The snapd and snap tools enable systems to work with .snap files.
Home Manager using Nix - Manage a user environment using Nix [maintainer=@rycee]
flatpak-external-data-checker - A tool for checking if the external data used in Flatpak manifests is still up to date
go-appimage - Go implementation of AppImage tools
org.qutebrowser.qutebrowser
bauh - Graphical user interface for managing your Linux applications. Supports AppImage, Debian and Arch packages (including AUR), Flatpak, Snap and native Web applications
snap-to-flatpak - A BASH script that removes Snap from an Ubuntu system and replaces it with Flatpak
AppImageUpdate - AppImageUpdate lets you update AppImages in a decentral way using information embedded in the AppImage itself.
Signal-Desktop - A private messenger for Windows, macOS, and Linux.