outline-server VS electron-builder

The same thing, waiting for solution. The one way is to watch for updates on github.

Doesn't seem to exist natively according to https://github.com/Jigsaw-Code/outline-server/issues/214 and https://github.com/Jigsaw-Code/outline-server/issues/257

It's private in that it's your own VM you're running the VPN on. No one else has access to it. Whether you trust Google or not, it's all open source[1].

[1] https://github.com/Jigsaw-Code/outline-server

Unless https://github.com/Jigsaw-Code/outline-server/issues/161 has changed, each access key only uses one core at the most.

https://github.com/Jigsaw-Code/outline-server/pull/415 but see https://github.com/Jigsaw-Code/outline-server/issues/44#issuecomment-451459926

Here is the CHANGELOG: https://github.com/Jigsaw-Code/outline-server/blob/master/src/shadowbox/CHANGELOG.md

We're currently adding a changelog to the server! It's in review now.

For connecting to a homelab, pick whichever of your servers can handle an another service and set up either Wireguard (ligthweight, common choice) or Outline (if you intend to connect often from a network that tends to block VPN traffic otherwise).

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.