- Notifications
You must be signed in to change notification settings - Fork109
-
ProblemCurrently there is a need to specify "db.password" to get proper information about the database. But as postgrestools.jsonc is committed to the repository, it should not contain any secrets, even local ones. I tried to find a solution, but couldn't find one that works for me. SuggestionTherefore I would like to suggest the ability to use .env or environment variables to set connection details. This allows a lot of flexibility for everyone. Example{// ..."db": {"host":"${POSTGRES_HOST}","port":"${POSTGRES_PORT}","username":"${POSTGRES_USERNAME}","password":"${POSTGRES_PASSWORD}",// <-- prevents potential leak of passwords"database":"${POSTGRES_DATABASE}",// ...}} |
BetaWas this translation helpful?Give feedback.
All reactions
Replies: 2 comments 3 replies
-
personally i'd love if more tools standardized on |
BetaWas this translation helpful?Give feedback.
All reactions
❤️ 2
-
That is also a possibility, but it's less flexible, I think. |
BetaWas this translation helpful?Give feedback.
All reactions
-
I don't believe it should be? it's just one fallback option when no explicit one is given |
BetaWas this translation helpful?Give feedback.
All reactions
-
Having the possibility to use |
BetaWas this translation helpful?Give feedback.
All reactions
-
thanks for the feedback! We are tracking something similar in#302. adding this to the issue 👍🏼 |
BetaWas this translation helpful?Give feedback.