How to build in a dev environment without publishing credentials
See original GitHub issue- Version: 19.56.0
- Target: macOS
The command $ electron-builder build
fails on a development environment because we are not providing AWS publishing credentials on local environments.
The error being thrown is CredentialsError: Missing credentials in config
.
Is there any way to build/package the app locally just for testing purposes without having to provide publishing credentials?
Issue Analytics
- State:
- Created 6 years ago
- Comments:11 (6 by maintainers)
Top Results From Across the Web
Publishing Credentials Sample - Gradle User Manual
Run ./gradlew publish and it will tell you what is missing right away, without executing the build. Credentials can and should be kept...
Read more >How to separate your credentials, secrets, and configurations ...
This article shows how to separate your credentials and configurations from the application source code with the environment variables and ...
Read more >Configure deployment credentials - Azure App Service
To retrieve the publishing credentials, go to the overview blade of your site and click Download Publish Profile. Use the file's FTP hostname, ......
Read more >Launch a dev environment - Docker Documentation
From Dev Environments in Docker Dashboard, select Create. The Create a Dev Environment dialog displays. Select Get Started. Optional: Provide a name for...
Read more >How to send Artifactory publish credentials from buildscript ...
1 Answer 1 · And if they are not found in the properties file (since you are running the build on a build...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Bug. Will be fixed evening CET. Thanks for log.
yeach… your bucket name is dotted —
releases.lbry.io