-
-
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
config.env should be overridden by runtime env variables #2209
Closed
oosawy opened this issue
Jun 15, 2024
· 1 comment
· Fixed by epacke/logstash-pipeline-tester#220, WomB0ComB0/gdsc-farmingdale-links-api#18, JuanPabloDiaz/food-RapidAPI#15, 0xgabrielpro/rentguard-backend#1 or Tugamer89/telegram_bus-bot#58
Closed
config.env should be overridden by runtime env variables #2209
oosawy opened this issue
Jun 15, 2024
· 1 comment
· Fixed by epacke/logstash-pipeline-tester#220, WomB0ComB0/gdsc-farmingdale-links-api#18, JuanPabloDiaz/food-RapidAPI#15, 0xgabrielpro/rentguard-backend#1 or Tugamer89/telegram_bus-bot#58
Comments
🎉 This issue has been resolved in version 3.1.4 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
nodemon -v
: 3.1.3Expected behaviour
Runtime environment variables expected to override the
env
defined in config.Actual behaviour
Envs defined in
config.env
are always be set.Seeing dotenv etc. this is not the expected behavior.
Steps to reproduce
nodemon.json
If applicable, please append the
--dump
flag on your command and include the output here ensuring to remove any sensitive/personal details or tokens.The text was updated successfully, but these errors were encountered: