-
|
Per the Contributing note in the README, I wanted to check if a PR moving most of the compose environment/configuration variables to a .env file would be welcome, or if it is an intentional design choice to keep them in the compose.yaml? I have already done this in my own deployments using the below |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
|
it is wanted to have them in the compose.yaml since except for TZ no env is shared between containers, so it doesn't make sense to add envs to containers which don't use them, also .env files have no upside but the downside of now having two files |
Beta Was this translation helpful? Give feedback.
it is wanted to have them in the compose.yaml since except for TZ no env is shared between containers, so it doesn't make sense to add envs to containers which don't use them, also .env files have no upside but the downside of now having two files