-
-
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
electron-updater and private source code #2292
Comments
So I've gone ahead and tried this, and the result is new errors! I went ahead and added a setFeedURL with the following data:
and the error log shows the following:
When I follow the link shown (
Is the link being built incorrectly? What needs changing? Thanks again! |
|
Hi @develar, thanks for your reply. I have adjusted my
...and in my When I run my app, the log shows the following error:
Following the link above, I see this in my browser:
What am I missing? Thanks! |
Hoping this does not get buried as a "closed" issue! |
Hi, please re-open this issue! I am in the same exact situation with my project. |
+1 |
I see that you have defined build options in package.json, I had to face the same problem and found that defining build options in electron-builder.json (seperate file) fixes this issue. much like done by this guy: |
same issue but 401 |
Saludooo!!! Estoy actualmente en la misma problemática, alguien ha podido encontrar la solución? |
In a recent issue #2289 I learned that electron-updater requires a
GH_TOKEN
on each user's machine in order to download private GitHub Releases. Since my app is only meant for employees of my company, I'm wondering if I can include the token in my code, and serve the initial DMG internally.I got this idea from an issue over at
electron-updater-example
, which usessetFeedURL
:However the auto-updater docs say not to use
setFeedURL
:I understand the security risks in hardcoding a token into the code, but is it possible to allow an app using electron-updater to download updates from a private GitHub repo using this method somehow?
If not, would this be possible using S3 in a similarly private/closed source situation?
Thank you!
The text was updated successfully, but these errors were encountered: