webcrate VS electron-builder

Tool you linked is open source apparently (https://github.com/WebCrateApp/webcrate) so you should be able to self-host it on your own. They have no specific docs for it though...

Hey fellow internet users! I always got frustrated with existing bookmarking tools as they were either too clunky to use or had way too many features I didn't need. Until I decided to just build my own!

WebCrate allows you to organize links, articles and more from around the web into collections called crates. You can share the crates with anyone and since each user gets their own instance of WebCrate in their own 'personal cloud' thanks to Deta Space, you can subscribe to other users crates and view their links right from your dashboard.

Learn more at http://webcrate.app or install it directly on Deta Space (https://deta.space/discovery/webcrate)! Let me know what you think (WebCrate is OSS, so you can also contribute) and I hope you find it useful!

👨‍💻 WebCrate is also open source, report any issues you find, suggest features, or contribute directly with code on GitHub!

WebCrate helps you organize and share links, articles and more from around the web in a central place. It's open source & can be easily self-hosted thanks to your own personal cloud in Deta Space.

WebCrate is completely separate from the browser. You can learn more on the homepage: webcrate.app.

https://webcrate.app - OSS bookmarking tool to help you organize your web

- Vue / Nuxt / Plain CSS

- TypeScript / Node / Express

- Hosted in your own personal cloud thanks to Deta Space (https://deta.space/discovery/webcrate)

Nuxt made the frontend super simple and fast to build, it takes care of a lot of things for you! Deta is also awesome for devs

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.