-
Notifications
You must be signed in to change notification settings - Fork 490
Auto Updates #149
Comments
I had a quick look recently on this as well. It seems like it would have to change the os x and windows installers to use squirrel, so a major change from the current workflow tools. Apart from those two platforms, there is no alternative for linux, so it seems like generating the deb file would remain the same. Personally I would welcome the change, but I can understand if some boilerplate users would not want to package their apps with squirrel. |
Yes, I also see the value here. And for sure finally will have to wrestle with this problem. My main concern is that it should be also easy to unplug (turn off) and should be easy to plug into real server-distribution workflow without actually implementing it here (I hope this thought sounds sane ;) ). Does someone who's reading my words use this boilerplate with auto-update? If so how many changes was required to make it work? |
Damn, I need the auto-update right now. Why don't we offer this as an alternative to |
The boilerplate would have to maintain two different installers. |
Ain't this what the boilerplate is there for? Bundling stuff so that we as app developers ain't got so much to do? Will try hacking on this. |
This project's build process was designed when such packages like mentioned here: #172 weren't there yet, or were so immature that I was afraid of using them. Now I consider this part of electron-boilerplate a legacy, and I'm willing to switch into mainstream tools if it won't do harm to any of the current features this boilerplate has. Any help in this area is greatly appreciated. I must start myself by getting familiar with that build tools and what they actually offer. |
Can we close this issue? |
After looking at how electron handles updates it looks like there are some ways to handle updates. It sounds like a common enough issue to be part of the boiler plate.
https://github.com/electron/electron/blob/master/docs/api/auto-updater.md
The text was updated successfully, but these errors were encountered: