-
Notifications
You must be signed in to change notification settings - Fork 1.1k
Support for reading env from .env files #12010
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
base: 4.10.x
Are you sure you want to change the base?
Conversation
|
This is not full support for dot env format. Need to imrove this integration. Also need to add support of multiple environments Links: https://hexdocs.pm/dotenvy/dotenv-file-format.html |
sdelamo
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the contribution. Can you add documentation?
sdelamo
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Could you clarify why .env files would be preferred instead of using .properties files?
|
This PR needs improvements as suggested by altro3. I will add documentation along with those changes in the next update. .env files are preferred for sensitive information like API keys and database passwords that shouldn't be committed to the git repo, unlike .properties files which are typically version controlled. |
Closes #11994.