From 0c2a8ca501b5e6e4c7bdb184b1b7e51d158c9d9f Mon Sep 17 00:00:00 2001 From: fabriciojs Date: Thu, 22 Dec 2022 08:15:55 -0300 Subject: [PATCH] added tip on variable names on kool.yml --- docs/1-Getting-Started/3-How-it-works.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/docs/1-Getting-Started/3-How-it-works.md b/docs/1-Getting-Started/3-How-it-works.md index 180ebea0..eb53dd7c 100644 --- a/docs/1-Getting-Started/3-How-it-works.md +++ b/docs/1-Getting-Started/3-How-it-works.md @@ -94,6 +94,8 @@ For example, use the `artisan` script in Laravel's **kool.yml** as follows: kool run artisan tinker ``` +> **Tip**: be careful with the syntax of the environment variables used in scripts within `kool.yml`. It's recommended that you always escape the variable name properly to avoid parsing issues: `${ENV_NAME}` - by using `${}` you make explicit the boundaries of the variable name helping, thus to avoid confusion. + #### Types of Commands The **kool.yml** file is not just for **kool** commands. You can add any type of command that you usually run in your shell, such as `cat`, `cp`, `mv`, etc.