From 662caa6f4873768fbd5099c9a1f61ce80ebe46dc Mon Sep 17 00:00:00 2001 From: DoTheEvolution Date: Wed, 13 May 2020 22:23:40 +0200 Subject: [PATCH] update --- README.md | 11 ++++++----- 1 file changed, 6 insertions(+), 5 deletions(-) diff --git a/README.md b/README.md index 2701cf0..b88e1de 100644 --- a/README.md +++ b/README.md @@ -41,9 +41,9 @@ Sometimes the `.env` file is used as `env_file` Variables set there are available during the building of the container, but unless named in the `enviroment:` option they are not available in the running containers. -* `env_file` - an option in compose that defines existing external file.
- Variables set in this file will be available in the running container, - but not in compose. +* `env_file` - an option in compose that defines an existing external file.
+ Variables in this file will be available in the running container, + but not during building of the container. So to not have polluted huge ass compose file, or to not have multiple places where changes need to be made when adding a variable... `env_file: .env` BAM. @@ -82,8 +82,9 @@ or backup a directory when its just there, sitting on the host. For sending emails free sendgrid account is used, which provides 100 free emails a day. -The configuration in `.env` files is almost universal, `apikey` is really username. -Only the password changes as it is one of yours accounts apikey value. +The configuration in `.env` files is almost universal, `apikey` is +really the username, not some placeholder. +Only the password changes, which you generate in apikey section on SendGrid website. ---