Question: Converting from nsis to nsis-web

Version: 15.4.2

Hey. I believe I asked this already but I want to be 100% positive/understand everything (don’t need anymore random uninstall nukings of people’s C drives lol).

We have an application currently in beta and we have been using the nsis packager. We will be switching to the nsis-web packager soon as we want to have both 64 and 32 bit supported. Right now we have just been distributing 64 bit. We plan on adding 32 bit this week.

When we create the new installer we will have a 32 bit 7z and a 64 bit 7z. Will the existing clients understand how to parse the latest.yml?

Normally when building a client (with nsis) I get:

win-unpacked/
Badlion Client Setup 0.9.6.exe
latest.yml

Now I am getting

nsis-web/latest.yml
win-ia32-unpacked/
win-unpacked/
Badlion Client Web Setup 0.9.6.exe
badlion-client-0.9.6-ia32.nsis.7z
badlion-client-0.9.6-x64.nsis.7z

(Side note [possible bug?]) the name from package.json is used for the .7z files instead of the productName. Not sure if this is going to cause issues or not. On this note the githubArtifactName is also using the name and not productName inside of latest.yml (not using this, just reporting it). Poking around inside of the web installer with a hex editor i don’t think either of these is an issue, but regardless reporting/asking to be safe.

version: 0.9.6
releaseDate: '2017-03-13T12:12:42.179Z'
githubArtifactName: badlion-client-WebSetup-0.9.6.exe
path: Badlion Client Web Setup 0.9.6.exe
sha2: eb874dc58af6984e443caaeb379cb232b4733e64e58642b43b7a8b6531c88b50

So my main questions after all of this information are:

1. Will it properly update from nsis to nsis-web with only 64 bit originally being supported?
2. Will updates properly happen for both 64 bit and 32 bit? How is it checking for an update? Is it checking the sha2/version of the latest.yml above for both versions and looking to see if there is a new one?
3. When uploading the files to the s3 bucket I have setup do i need to move the nsis-web/latest.yml up one directory to just be latest.yml again? Otherwise the old installers will be looking for the wrong path?

Thanks.

[develar]

since we actually are using cloudfront and not s3 to distribute the files anyways. Not sure if that is supported or not.

Specify 2 publish configs. First (provider: generic) will be used for update. All (second as provider: s3) will be used for publish.

.just adds another layer of possible problems

Yes, as web installer download file from internet, it is additional layer of possible problems. Connectivity issues are very rare, but still possible. Well, NSIS and used plugin is not a homemade, — tested and proven by numerous users (including Google/Dropbox if I am not wrong).

[develar]

Where is that current app version? Inside of the actual exe hardcoded somewhere?

https://github.com/electron/electron/blob/master/docs/api/app.md#appgetversion