Skip to content

Conversation

iamsb97
Copy link
Contributor

@iamsb97 iamsb97 commented Aug 26, 2025

Closes #11994.

@altro3
Copy link
Contributor

altro3 commented Aug 27, 2025

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
https://www.dotenv.org/docs/
https://dotenvx.com/docs/env-file
https://github.com/motdotla/dotenv
https://github.com/radprogrammer/dotenv-RFC

Copy link
Contributor

@sdelamo sdelamo left a 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?

Copy link
Contributor

@sdelamo sdelamo left a 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?

@sdelamo sdelamo added the type: enhancement New feature or request label Sep 8, 2025
@iamsb97
Copy link
Contributor Author

iamsb97 commented Sep 8, 2025

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: enhancement New feature or request
Projects
Status: No status
Development

Successfully merging this pull request may close these issues.

Support for reading env from .env files
3 participants