nsis-web appPackageUrl property causes 404 error on web installer #1810
Comments
…rty in config Installer did not find the file to download when using appPackageUrl, because the installer script was missing the file name. Fix electron-userland#1810
Sorry for late response. It is by design, in the docs "URL like To provide own url — configure publish. e.g. generic provider.
|
Sorry, didn't notice was by design. In my case I don't have full control of the server, so I cannot send the correct zip file (ia32 or x64) for the client installer, since I cannot read the header of the request. I had to created 2 JSON config files, one for the NSIS Full Setup and another for the NSIS Web, and run the packaging 2 times. |
@xavero You are not forced to specify publish options for all targets. Simply specify it in the |
I feel dumb now.. I didn't realize that publish options was also a property for the nsis and nsisWeb targets... I was only setting in the root level. Yes, I think that will work for me. Thanks for all the help. |
Version: 19.13.0
Target: nsis and nsis-web
When I define the appPackageUrl property in nsis-web section, the web installer cannot download the 7zip files, because the installer script don't append the filenames to the Package Url
Example:
npm install && npm run installer
The text was updated successfully, but these errors were encountered: