deezer-linux VS electron-builder

Some of the UI changes I find hard to adjust to, but that alone is not a good reason. The lack of Linux support is something I'll never understand, considering they made the Windows app using a framework that is cross-platform by default. I feel like Deezer just doesn't want to bother testing it on Linux. The unofficial community port of the app works just fine though.

I'm using fedora too and i've installed this client https://github.com/aunetx/deezer-linux/releases/tag/v5.30.220-2. It's chromium so FLAC should work as intended

However, if you wish you had native experience on Linux, check https://github.com/aunetx/deezer-linux. I have been using it on Ubuntu for a couple of months, and it 100% integrates with the OS; it's not a web app running inside a single-use web browser.

Did you know about this: https://github.com/aunetx/deezer-linux/releases

Is this what you are talking about ? https://www.deezer.com/us/ https://github.com/aunetx/deezer-linux

How about this? A Linux port of the Windows desktop app here. Download the deb package, right-click in the files app and install directly into your Linux container. A launch icon is placed in the Linux apps folder. Alternatively, download the appimage to your Linux files folder, make it executable in Terminal with sudo chmod +x file.appimage then run it from Terminal by entering ./file.appimage. Both appear to work in my container (Debian Bullseye in Chrome OS 97 stable channel).

download the repo: git clone https://github.com/aunetx/deezer-linux && cd deezer-linux

The last step for each platform's build process is to upload the app to our GitHub releases repository. We automated this step from the beginning, but when we started creating builds for the new M1 chip Macs, we had to add a manual step. This involved merging files needed for the auto-updater to work with the M1 builds.

https://github.com/electron-userland/electron-builder/issues... that issue kinks to the PR that adds the automation.

It's a non-trivial thing to test, since it involves so many secrets and the notarization step can take over an hour, so I don't expect anyone here to actually want to look into it.

My original comment really was just venting my frustration, not a cry for help (but I might be crying soon if I can get to the bottom of this!).

> The ‘autoupdater’ does three things,

>

> - check the app for updates (using Sparkle)

> - report any crashes (using Sentry)

> - start a local HTTP proxy on port 40701 (this can be changed using the configuration json file in the app bundle).

>

> The latter is of course, not to be expected of any app on the machine, especially not one that just claims to be an auto updater.

Well, yes. And no.

For example, electron-builder [^0], a popular framework used for Electron app packaging and auto-updates, uses a local update server on Mac [^1] to add a more sane system backed by a more insane system, Squirrel.

[^0]: https://github.com/electron-userland/electron-builder

[^1]: https://github.com/electron-userland/electron-builder/blob/m...

The Project uses Electorn-Builder to package the app and Electorn-Updater to update.

You can read about this issue here: https://github.com/electron-userland/electron-builder/issues/7114

Ostara is based off of electron-react-boilerplate and uses electron-builder to package the application.

Install electron and electron-builder

I believe Visual Studio Code uses Electron and posts releases on a regular basis. Maybe check their A quick Google search for "electron build github release" turns up "Electron Builder" https://www.electron.build/ I don't really know though; I've never used Electron.

I also would like to have an NSIS installer so if it happens to package the Chromium executable along with my app, how can I accomplish that? I am using electron-builder.

We use electron-builder at work.