Use .env files in the docker-compose.yaml file #11
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Using .env file in the
docker-compose.yaml
file could greatly improve the configuration process by preventing the user from modifying a potentially "scary" compose file but instead modify an intuitive file with only the configurable values.Use .env file instead of directly modifying the docker-compose.yaml fileto Use .env files in the docker-compose.yaml fileThis idea will be abandoned because the configuration cannot be resumed to only the environment file : the volumes are as likely to be changed by the user as the environment variable, and splitting everything might just end up be confusing for them.