Not setting NODE_ENV to production.
See original GitHub issueHey,
I have a project which is deployed to GAE and is using this image as base, but i want to deploy a dev version of this app.
I’ve created a simple app-dev.yaml
file, which looks like this:
service: dev-api
runtime: custom
vm: true
threadsafe: false
env_variables:
NODE_ENV: development
But it isn’t picked up by Dockerfile, is there any way to work around this?
Issue Analytics
- State:
- Created 7 years ago
- Comments:7 (4 by maintainers)
Top Results From Across the Web
node.js - How can I set NODE_ENV=production on Windows?
If you're in CMD (which is no longer maintained), use set NODE_ENV=production. This should be executed in the command prompt where you intend...
Read more >NODE_ENV not set on process.env · Issue #2362 · webpack ...
This will NOT print anything. Run NODE_ENV=production && webpack --silent --mode=production && echo $NODE_ENV. This will print production.
Read more >How can I set NODE ENV production on Windows - Edureka
At the command line: set NODE_ENV=production&&npm start. or set NODE_ENV=production&&node index. · The trick for it to work on Windows is you ...
Read more >Do not use NODE_ENV for staging - Gleb Bahmutov
When running on staging or production, I set NODE_ENV variable on the server to staging or production . This value then lets my...
Read more >What is Node_ENV Production and How to Get it on Windows ...
Set node_env =production & node whatever if you're using git bash on Windows. Js does not seem to function. Use the native cmd...
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
Interesting - we’ll do some testing to figure out why this isn’t working. In the meantime - can you try setting the env var via your Dockerfile? Try adding this:
My guess is that we have a bug with the interaction between env vars set by Flex and env vars set in the base dockerfile.
Hi, I’ve been trying to pass env_variables from the app.yaml with cutom runtime to the dockerFile and the value I read for it is empty, any advice ?
However, when i try to read its value i see it empty: