Environment variables not populated in .env
See original GitHub issueUsing React + Node.js with MongoDB flavor of Cosmos db.
Below is what my .env
file looks like. Even though a database was successfully created and deployed, the configuration was not updated.
Web Template Studio will automatically add Cosmos Keys to this file once your database has been deployed.
To manually retrieve your Cosmos database connection string and keys, follow these docs (https://docs.microsoft.com/en-us/azure/cosmos-db/mongodb-mongoose)
COSMOSDB_CONNSTR=mongodb://{cosmos-user}.documents.azure.com:10255/{dbname}
COSMOSDB_USER=cosmos-user
COSMOSDB_PASSWORD=cosmos-secret
Issue Analytics
- State:
- Created 4 years ago
- Comments:5 (1 by maintainers)
Top Results From Across the Web
No results found
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
I created a new project and can confirm that the popup appeared. The
.env
file was populated as expected.@henryjw I’ve also had an impression that something went wrong when WebTS was creating CosmosDB instance. It took around 2 minutes to show the popup that @dgomezc is referring to. But in the end it worked well.