ELECTRON AUTO UPDATE WITH CUSTOM STATIC SERVER (NON PUBLIC GIT REPO, need custom authentication)

suppose we have 0.0.1 version and we want to let auto update to versin 0.0.2.

according to electron doc: Updating Applications

you could host your one on updates.electron or some other platform.

But we need have binaries behind authencation. also hosting on github is not option, we need to hosted somewhere freely like OSS in china(not officially supported) or some server.

MANUALLY

Because the requests made by Auto Update aren't under your direct control, you may find situations that are difficult to handle (such as if the update server is behind authentication). The url field does support files, which means that with some effort, you can sidestep the server-communication aspect of the process. Here's an example of how this could work.

Good post from joshuapinter on this issue.

SOME TWEAKS

• use electron-download-manager to download nupkg and RELEASES files - (from npm run make)
• use electron-log to somehow log file ( you could check that log when running)
• host those two files in some server or static file services

ORIGIN REPO:

Update Rocks! Electron

This is our electron applicatino which integrate Update Rocks! You can learn more about how it works here : https://www.update.rocks/howto

It also have the travis and travis scripts which automatically publish the assets in a release when a tag is created.

Install dependencies

$ npm install

Dev

$ npm start

Build

$ npm run make