I am responsible for maintaining Cryptomator desktop applications and we’ve decided to switch from the .deb/.rpm/ppa/aur/etc hell to using AppImages for our upcoming release.
Now that I’ve managed to create the AppImage itself on TravisCI (still have some questions, but that would be a different topic), we need to decide what is the best way of publishing it. @probono has suggested to use GitHub releases in this GitHub issue. We’re currently working with Bintray for our Windows and Mac applications.
Bintray is significantly faster (at least in my region) than GitHub Releases, which play a role if central directories such as AppImageHub or eventually package managers link to it.
Furthermore, GitHub Releases only work for tagged commits which requires some extra work for nightly builds (I don’t mean the tagging itself but rather the CI config gets more complex). Having source code and releases on the same service is more consistent, though.
Once we have published it, what would be the ideal instruction for users not familiar with AppImages? Apart from making the AppImage executable after download, should I recommend saving it to
~/bin as suggested by the Wiki or
~/Applications which is also watched by appimaged? In my opinion
~/Applications would be an easy-to-understand location for technically less advanced users. But Linux purists surely don’t like it as much as
- Where to upload AppImages?
- What service is easiest to integrate with AppImageUpdate and AppImageHub?
- How do I write good download instructions?