-
Notifications
You must be signed in to change notification settings - Fork 132
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
.env Port variables not named PORT are not being used #145
Labels
Comments
The above was run on Windows machine. I just ran it on my Mac and the environment variables are working fine as expected. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
If I use
PORT
in.env
like so it will use the port defined in the environment file.If I try to use something like
DB_PORT
it will default to 5000I've looked through previous issues and I cannot tell if this is expected functionality or not. If it is, some added documentation about it would be helpful. Previously closed issues made it sound like the first example I gave should not work, yet it does.
If it's going to automatically assign the ports is there a way for me to access those in my scripts given that they're not matching what I threw into the
.env
file. (I guess I could pass it in as an argument to the script if supported, assume the same variable will contain the same port per line and not increment per read)The text was updated successfully, but these errors were encountered: