diff --git a/docs/Lama2/docs/explanation/l2configAtRoot.png b/docs/Lama2/docs/explanation/l2configAtRoot.png deleted file mode 100644 index 7ca55e51..00000000 Binary files a/docs/Lama2/docs/explanation/l2configAtRoot.png and /dev/null differ diff --git a/docs/Lama2/docs/explanation/l2env.png b/docs/Lama2/docs/explanation/l2env.png deleted file mode 100644 index a9a98e1c..00000000 Binary files a/docs/Lama2/docs/explanation/l2env.png and /dev/null differ diff --git a/docs/Lama2/docs/explanation/l2envOverideL2config copy.png b/docs/Lama2/docs/explanation/l2envOverideL2config copy.png deleted file mode 100644 index 541a2db6..00000000 Binary files a/docs/Lama2/docs/explanation/l2envOverideL2config copy.png and /dev/null differ diff --git a/docs/Lama2/docs/explanation/l2envOverideL2config.png b/docs/Lama2/docs/explanation/l2envOverideL2config.png deleted file mode 100644 index df8b877f..00000000 Binary files a/docs/Lama2/docs/explanation/l2envOverideL2config.png and /dev/null differ diff --git a/docs/Lama2/docs/explanation/l2format.md b/docs/Lama2/docs/explanation/l2format.md index 0faa87ea..7f3e4ce6 100644 --- a/docs/Lama2/docs/explanation/l2format.md +++ b/docs/Lama2/docs/explanation/l2format.md @@ -113,7 +113,7 @@ and its contents are loaded to create a set of variables (local). In the `l2.env` file, you can specify environment-specific values for variables used in your L2 scripts, such as URLs, authentication tokens, or any other data that may vary depending on the environment in which the API requests are executed. -![l2.env at API level](l2env.png) +![l2.env at API level](../tutorials/l2env.png) Go to [Example](../tutorials/examples.md#case-1-l2env-adjacent-to-an-api-file) @@ -125,7 +125,7 @@ The `l2config.env` file serves as a centralized storage for environment variable The search for `l2config.env` extends from the present directory up to the root directory (`/`). During this process, the variables defined in the root file are loaded and made available for use in all relevant scripts. This approach significantly enhances efficiency and maintainability, as it ensures consistent settings throughout the project while reducing redundancy in configuration data. -![l2config.env at Project root level](l2configAtRoot.png) +![l2config.env at Project root level](../tutorials/l2configAtRoot.png) Go to [Example](../tutorials/examples.md#case-2-root-variables) @@ -137,7 +137,7 @@ In situations where both root and local variables share the same variable name, The local variable's value will always be considered over the root variable, ensuring that specific configurations defined at the local level effectively override any corresponding settings present in the root file. This approach provides developers with granular control and flexibility in tailoring environment variables to suit specific needs within different parts of the project while maintaining the overall structure and organization of configuration settings. -![l2config.env at Project root level](l2envOverideL2config.png) +![l2config.env at Project root level](../tutorials/l2envOverideL2config.png) Go to [Example](../tutorials/examples.md#case-3-override-root-variable-with-local-variable) diff --git a/docs/Lama2/site/explanation/l2configAtRoot.png b/docs/Lama2/site/explanation/l2configAtRoot.png deleted file mode 100644 index 7ca55e51..00000000 Binary files a/docs/Lama2/site/explanation/l2configAtRoot.png and /dev/null differ diff --git a/docs/Lama2/site/explanation/l2env.png b/docs/Lama2/site/explanation/l2env.png deleted file mode 100644 index a9a98e1c..00000000 Binary files a/docs/Lama2/site/explanation/l2env.png and /dev/null differ diff --git a/docs/Lama2/site/explanation/l2envOverideL2config copy.png b/docs/Lama2/site/explanation/l2envOverideL2config copy.png deleted file mode 100644 index 541a2db6..00000000 Binary files a/docs/Lama2/site/explanation/l2envOverideL2config copy.png and /dev/null differ diff --git a/docs/Lama2/site/explanation/l2envOverideL2config.png b/docs/Lama2/site/explanation/l2envOverideL2config.png deleted file mode 100644 index df8b877f..00000000 Binary files a/docs/Lama2/site/explanation/l2envOverideL2config.png and /dev/null differ diff --git a/docs/Lama2/site/explanation/l2format.html b/docs/Lama2/site/explanation/l2format.html index daa5593f..03ebd908 100644 --- a/docs/Lama2/site/explanation/l2format.html +++ b/docs/Lama2/site/explanation/l2format.html @@ -1018,19 +1018,19 @@
In the l2.env
file, you can specify environment-specific values for variables used in your L2 scripts, such as URLs, authentication tokens, or any other data that may vary depending on the environment in which the API requests are executed.
Go to Example
Get Source File
l2config.env
¶The l2config.env
file serves as a centralized storage for environment variables located at the project root, streamlining the management of configuration settings across all L2 scripts. With this file present, every L2 script within the project automatically inherits the defined variables, effectively eliminating the necessity to duplicate configurations in individual subdirectories using l2.env
.
The search for l2config.env
extends from the present directory up to the root directory (/
). During this process, the variables defined in the root file are loaded and made available for use in all relevant scripts. This approach significantly enhances efficiency and maintainability, as it ensures consistent settings throughout the project while reducing redundancy in configuration data.
Go to Example
Get Source File
l2config.env
(root) variables are redeclared in l2.env
(local)¶In situations where both root and local variables share the same variable name, the local variable takes precedence over the root variable. This behavior remains consistent, even if both l2config.env
(root) and l2.env
(local) files reside in the same directory.
The local variable's value will always be considered over the root variable, ensuring that specific configurations defined at the local level effectively override any corresponding settings present in the root file. This approach provides developers with granular control and flexibility in tailoring environment variables to suit specific needs within different parts of the project while maintaining the overall structure and organization of configuration settings.
-Go to Example
Get Source File