Add Built-in AppImage Maker
See original GitHub issueSee: https://en.wikipedia.org/wiki/AppImage
I would rather not have code that calls the AppImage creator inside of Electron Forge, but rather it should be a separate package like the ones for .deb
, .rpm
, and Flatpak. (electron-installer-appimage
?)
Issue Analytics
- State:
- Created 7 years ago
- Reactions:15
- Comments:32 (5 by maintainers)
Top Results From Across the Web
Add Built-in AppImage Maker #26 - electron/forge - GitHub
You can use electron-builder only to build prepackaged app into distributable format (AppImage, Snaps). ./node_modules/.bin/build --prepackaged ...
Read more >Making AppImages updateable
To make an AppImage updateable, you need to embed information that describes where to check for updates and how into the AppImage. Unlike...
Read more >Tutorial — appimage-builder 1.0.0 documentation
The first step in our process is to build the application binaries. We will set the install prefix to '/usr' as appimage-builder expects...
Read more >How to Easily Integrate AppImages into your Linux Desktop
AppImageLauncher will open a new window (Figure C), asking if you'd like to either Run Once or Integrate And Run. Click Integrate And...
Read more >Integrate and Manage AppImages with AppImageLauncher
AppImages are another of the portable package formats available in Linux allowing you to run software without installing packages on the ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@stevewillard I’ve forked @trusktr’s repository and done some improvements into the code. Currently I use my fork for my own Electron-based project.
Getting the same error @DinkoMiletic. Did you manage to fix it?