-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unable to publish when setting endpoint url to CloudFront #2414
Comments
Could you please provide full error? Is publish successful? |
Cloudfront won't take S3 upload requests, so you can not point However, it'd be really great to allow specify the front-end |
@bithavoc You can set 2 publish providers, first one will be used for electron-updater, all will be used to publish (so, as you said, just use GenericServerOptions for CouldFront). |
Did anyone get this working? What I am really looking for is:
Is it enough to set up GenericServer (CloudFront) as first on the list, and S3 as second? Then publish will upload to S3 all files, but use CF to fetch the files? |
You can set the publish config as S3 in autoUpdater.setFeedURL({
provider: 'generic',
url: 'https://anydomain.com/',
})
autoUpdater.checkForUpdatesAndNotify() |
I was investigating a similar case.
|
We have this app that we're about to distribute globally using S3 + CloudFront.
S3 is setup correctly and I can publish as usual using
build --mac --win -p always
, but if I set thepublish.endpoint
option to the CloudFront URL (e.g. https://d3tpy77yecs5fp.cloudfront.net) it fails with:Error: Cannot Cleanup [...] XMLParserError: Unexpected close tag
Is S3 + CloudFront supported? Do I need to use
setFeedURL
?Thanks
The text was updated successfully, but these errors were encountered: