Bazecor VS electron-builder

Sadly I agree. Splits are great. I am eagerly awaiting my ortholinear split keyboard from https://dygma.com/ - no affiliation other than being a customer of their first keyboard, the raise and having the defy on order.

Maybe it's just me, but I think the proliferation of mechanical keyboards brings people closer to the fringe where custom keyboards, layouts, parts and pcbs are the norm for the pursuit of perfection.

Windows | Mac Arm | Mac Intel | Linux

The software is open-source and you can fork it if you want. Here's the link to our Github: https://github.com/Dygmalab/Bazecor 😊

I have tried passing the disable shm flag without any luck (disable-dev-shm-usage). The repo is https://github.com/Dygmalab/Bazecor/tree/blacksmith

Dygma Raise or Defy.

Bazecor 1.1.2 Firmware v1.0.9beta

This bug is still not fixed after 2 years and it's very disappointing. I use OSL for almost all layers except for macro layer, which I use Shift to Layer.

Found this https://github.com/Dygmalab/Bazecor/issues/90 where someone figured out F20 is triggering XF86AudioMidMute in Linux. So, this may not need any custom QMK firmware at all, and could be as easy as assigning F20 to some key with VIA and see if that does what you need. F20 is available in the VIA Configure (keyboard icon) Tab under Special down on the lower left side.

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.