[GH-ISSUE #3845] [FEAT]: Include Appimages in Releases #2455

Closed
opened 2026-02-22 18:29:45 -05:00 by yindo · 2 comments
Owner

Originally created by @IfGremlinThen on GitHub (May 19, 2025).
Original GitHub issue: https://github.com/Mintplex-Labs/anything-llm/issues/3845

What would you like to see?

I don't understand the point of funneling Linux users into using a bash script that downloads a fixed .appimage from an obfuscated .cdn domain page on your website.

If they are included on the releases page, people can have version rollback and it's one less step to running the software, but instead you're making Linux users:

  • go to your website
  • go to the downloads page
  • groan at the sight of an "installer script"
  • read the installer script and find that it's actually curling an appimage
  • copy and paste the link into their browser instead of running the stupid script
  • and then post here to ask why the hell they had to do that

Who asked for their download process to be needlessly complicated? Linux users probably know how to the check executable permissions on a file and may even have a desktop integration that does that for them anyway. The appimage runs fine without you unpacking it and deleting the file I just downloaded, so what's the point?

Clearly you felt this way at some point because you were including appimages in your GitHub releases up until 1.4, after which I can only assume that your land was inexplicably conquered and devastated and your nation's history was destroyed in a massive book burning because there are no releases again until 1.7 a month later, at which point you have a decidedly colder and less transparent means of sharing your software.

EDIT: Oh, and Windows and Mac don't need an install script, wtf?

Originally created by @IfGremlinThen on GitHub (May 19, 2025). Original GitHub issue: https://github.com/Mintplex-Labs/anything-llm/issues/3845 ### What would you like to see? I don't understand the point of funneling Linux users into using a bash script that downloads a fixed .appimage from an obfuscated .cdn domain page on your website. If they are included on the releases page, people can have version rollback and it's one less step to running the software, but instead you're making Linux users: - go to your website - go to the downloads page - groan at the sight of an "installer script" - read the installer script and find that _it's actually curling an appimage_ - copy and paste the link into their browser instead of running the stupid script - and then post here to ask why the hell they had to do that Who asked for their download process to be needlessly complicated? Linux users _probably know_ how to the check executable permissions on a file and may even have a desktop integration that does that for them anyway. The appimage runs fine without you unpacking it and deleting the file I just downloaded, so what's the point? Clearly you felt this way at some point because you were including appimages in your GitHub releases up until 1.4, after which I can only assume that your land was inexplicably conquered and devastated and your nation's history was destroyed in a massive book burning because there are no releases again until 1.7 a month later, at which point you have a decidedly colder and less transparent means of sharing your software. **EDIT:** Oh, and Windows and Mac don't need an install script, wtf?
yindo added the enhancementfeature request labels 2026-02-22 18:29:45 -05:00
yindo closed this issue 2026-02-22 18:29:45 -05:00
Author
Owner

@timothycarambat commented on GitHub (May 19, 2025):

They are now all linked in the changelogs, that's why. Not sure what the theatre is all about but it was fun to read

@timothycarambat commented on GitHub (May 19, 2025): They are now all linked in the changelogs, that's why. Not sure what the theatre is all about but it was fun to read
yindo changed title from [FEAT]: Include Appimages in Releases to [GH-ISSUE #3845] [FEAT]: Include Appimages in Releases 2026-06-05 14:46:40 -04:00
Author
Owner

@KhazAkar commented on GitHub (May 27, 2026):

I would definitely propose having them in releases in github, because it can help with some... issues downloading :)

<!-- gh-comment-id:4552682138 --> @KhazAkar commented on GitHub (May 27, 2026): I would definitely propose having them in releases in github, because it can help with some... issues downloading :)
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Mintplex-Labs/anything-llm#2455