From 08db32b37c4a7e2cee037cf6fd8fb42a91ae922d Mon Sep 17 00:00:00 2001 From: Philipp Melab Date: Mon, 25 Oct 2021 10:19:11 +0200 Subject: [PATCH 1/2] docs: add hint about where to put .env files Make clear that `.env` and `.lagoon.env` files are loaded relative to `WORKDIR`. --- docs/using-lagoon-advanced/environment-variables.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/using-lagoon-advanced/environment-variables.md b/docs/using-lagoon-advanced/environment-variables.md index 47c68e1226..d45367204e 100644 --- a/docs/using-lagoon-advanced/environment-variables.md +++ b/docs/using-lagoon-advanced/environment-variables.md @@ -14,7 +14,7 @@ As there can be environment variables defined in either the Dockerfile or during 6. Environment variables defined in `.env`. 7. Environment variables defined in `.env.defaults`. -`.lagoon.env.$BRANCHNAME`, `.lagoon.env.$BRANCHNAME`, `.env`, and `.env.defaults` are all sourced by the individual containers themselves as part of running their entrypoint scripts. They are not read by Lagoon, but by the containers themselves. +`.lagoon.env.$BRANCHNAME`, `.lagoon.env.$BRANCHNAME`, `.env`, and `.env.defaults` are all sourced by the individual containers themselves as part of running their entrypoint scripts. They are not read by Lagoon, but by the containers `ENTRYPOINT` scripts, which look for them in the containers working directory. If environment variables don't appear as expected, check if your container has a `WORKDIR` setting that that points to somewhere else. ## Environment Variables \(Lagoon API\) From f537051f861e5c4f7c31a18525c490d83a870f65 Mon Sep 17 00:00:00 2001 From: Philipp Melab Date: Mon, 25 Oct 2021 10:20:47 +0200 Subject: [PATCH 2/2] Update environment-variables.md --- docs/using-lagoon-advanced/environment-variables.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/using-lagoon-advanced/environment-variables.md b/docs/using-lagoon-advanced/environment-variables.md index d45367204e..768169fe50 100644 --- a/docs/using-lagoon-advanced/environment-variables.md +++ b/docs/using-lagoon-advanced/environment-variables.md @@ -14,7 +14,7 @@ As there can be environment variables defined in either the Dockerfile or during 6. Environment variables defined in `.env`. 7. Environment variables defined in `.env.defaults`. -`.lagoon.env.$BRANCHNAME`, `.lagoon.env.$BRANCHNAME`, `.env`, and `.env.defaults` are all sourced by the individual containers themselves as part of running their entrypoint scripts. They are not read by Lagoon, but by the containers `ENTRYPOINT` scripts, which look for them in the containers working directory. If environment variables don't appear as expected, check if your container has a `WORKDIR` setting that that points to somewhere else. +`.lagoon.env.$BRANCHNAME`, `.lagoon.env.$BRANCHNAME`, `.env`, and `.env.defaults` are all sourced by the individual containers themselves as part of running their entrypoint scripts. They are not read by Lagoon, but by the containers `ENTRYPOINT` scripts, which look for them in the containers working directory. If environment variables don't appear as expected, check if your container has a `WORKDIR` setting that points to somewhere else. ## Environment Variables \(Lagoon API\)