Environment Variables Explained: Settings Outside Your Website Code

The six points in the video

This is a silent video. The headings, explanations and labels below reproduce the information on screen.

1. 1

   Step 1: A variable has a name and value

   0:18

   The application reads the named setting when it needs it.

   On-screen labels: Setting name; Configured value; Application use.

2. 2

   Step 2: Environments can differ

   0:30

   A test environment can use different values from production.

   On-screen labels: Local development; Preview settings; Production settings.

3. 3

   Step 3: Check when the value is read

   0:42

   A value may be used during a build or while the application runs.

   On-screen labels: Build-time use; Runtime use; Framework behaviour.

4. 4

   Step 4: Some values are sensitive

   0:54

   Tokens and credentials need protected storage and restricted access.

   On-screen labels: Private credentials; Protected storage; Limited access.

5. 5

   Step 5: Browser values are public

   1:06

   A value included in downloaded website code can be inspected.

   On-screen labels: Browser bundle; Visible configuration; No private secrets.

6. 6

   Step 6: Check how changes take effect

   1:18

   Follow the platform process and test the updated deployment.

   On-screen labels: Correct environment; Required rebuild; Verified behaviour.

Common questions

Go further