Electron-forge: Configuring AutoUpdate

[Skizu]

• [x] I have read the contribution documentation for this project.
• [x] I agree to follow the code of conduct that this project follows, as appropriate.
• [x] I have searched the issue tracker for an issue that matches the one I want to file, without success.

Please describe your issue:
How do I configure auto updates, I've been looking through all your documentation, issues and tickets, and I am unable to find anything to do with how to configure auto updates based off the publisher config.

[MarshallOfSound]

@Skizu Electron forge doesn't have much to do with your autoUpdater configuration, the only bit they vaguely connect on is the "publish" config.

For the github publish target you want to host an update server like nuts and point it at the same repository you pointed forge at.

For the ers publish target you want to host an instance of electron-release-server and follow their documentation on how to configure the autoUpdater module.

[LeandroRezendeCoutinho]

Hello @MarshallOfSound. The problem is that there is no any example of a complete configuration.
Everything sonds like magic.
Can you indicate where to find file, server configurations?
Thanks

[joshuapinter]

@LeandroOnLine Did you ever find a complete example of how to do this? We're struggling with the same thing. Thanks!

[malept]

https://github.com/electron/update.electronjs.org (which you can probably self-host if you're not an open source app) contains an example of autoupdating using the update-electron-app module with Electron Forge.

[joshuapinter]

@malept I actually ended up creating a new public github repo just for our app's releases, which allowed us to use update.electronjs.org's update server, which works exceptionally well. Everything is working great now.

Honestly, I wish I started with this instead of going down the path of nuts, hazel, electron-release-server, etc. This is much simpler.

Thanks!