selfhosted
/
selfhosted-apps-docker
mirror of https://github.com/DoTheEvo/selfhosted-apps-docker.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity

update

This commit is contained in:
DoTheEvolution 2020-06-24 21:12:31 +02:00
parent d5e9bb56fa
commit 6a73e221b1
1 changed files with 11 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

17
README.md
View File

@ -65,14 +65,19 @@ Often the `.env` file is used as `env_file`
So a setup having `env_file: .env` in the compose mixes these two together.
Benefit is that you do not need to make changes at multiple places,
adding variable or changing its name in `.env` does not require
to also go in to compose to add/change it there..</br>
adding variable or changing a name in `.env` does not require
to also go in to compose to add/change it there...</br>
Also the compose file looks less cramped.
Only issue is that **all** variables from `.env` are available in
containers that use this `env_file: .env` method.</br>
That can lead to potential issues if you try to use this approach elsewhere,
universally.
Only issue is that **all** variables from the `.env` file are available in
all containers that use this `env_file: .env` method.</br>
That can lead to potential issues if some containers picks up enviroment
variable that is intented for a different container of the stack.
This is tested and works in all setups here, but if you start to use this
everywhere without understanding it, you can encounter unknown issues.
So first troubleshooting step should be abandoning `.env` and write out
the variables directly in the compose file.
---