Environment configuration in Laravel - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to load environment variables in Laravel.

Laravel

Dotenv::createImmutable(__DIR__)->[1]();

Drag options to blanks, or click blank then click option'

Ainit

Brun

Cload

Dstart

Attempts:

3 left

💡 Hint

Common Mistakes

Using methods like run or start which do not exist in Dotenv.

Confusing initialization with loading.

The load() method loads the environment variables from the .env file.

2fill in blank

medium

Complete the code to get the value of APP_ENV from environment variables.

Laravel

$environment = env('[1]', 'production');

Drag options to blanks, or click blank then click option'

AAPP_ENV

BAPP_DEBUG

CAPP_URL

DAPP_NAME

Attempts:

3 left

💡 Hint

Common Mistakes

Using APP_DEBUG which controls debug mode, not environment.

Using APP_URL or APP_NAME which are unrelated.

The env() helper fetches the value of the environment variable named APP_ENV.

3fill in blank

hard

Fix the error in the code to correctly set the database host from environment variables.

Laravel

'host' => env('[1]', '127.0.0.1'),

Drag options to blanks, or click blank then click option'

ADB_HOST

BDB_DATABASE

CDB_PORT

DDB_USERNAME

Attempts:

3 left

💡 Hint

Common Mistakes

Using DB_PORT which is for the port number.

Using DB_DATABASE which is the database name.

Using DB_USERNAME which is the user name.

The correct environment variable for the database host is DB_HOST.

4fill in blank

hard

Fill both blanks to set the mail driver and mail host from environment variables.

Laravel

'driver' => env('[1]', 'smtp'),
'host' => env('[2]', 'smtp.mailtrap.io'),

Drag options to blanks, or click blank then click option'

AMAIL_MAILER

BMAIL_DRIVER

CMAIL_HOST

DMAIL_PORT

Attempts:

3 left

💡 Hint

Common Mistakes

Using MAIL_MAILER instead of MAIL_DRIVER in older Laravel versions.

Confusing MAIL_PORT with MAIL_HOST.

Older Laravel versions use MAIL_DRIVER for mail driver, and MAIL_HOST for mail host.

5fill in blank

hard

Fill all three blanks to set cache driver, queue connection, and session driver from environment variables.

Laravel

'cache' => env('[1]', 'file'),
'queue' => env('[2]', 'sync'),
'session' => env('[3]', 'file'),

Drag options to blanks, or click blank then click option'

ACACHE_DRIVER

BQUEUE_CONNECTION

CSESSION_DRIVER

DCACHE_CONNECTION

Attempts:

3 left

💡 Hint

Common Mistakes

Using CACHE_CONNECTION instead of CACHE_DRIVER.

Mixing up QUEUE_CONNECTION and SESSION_DRIVER.

These are the standard environment variable names for cache, queue, and session drivers in Laravel.

Practice

1. What is the main purpose of the .env file in a Laravel project?

easy

A. To define routes and controllers

B. To write all application logic and functions

C. To store user data and session information

D. To store environment-specific configuration settings outside the code

Solution

1. Step 1: Understand the role of environment files

   The .env file is designed to keep configuration settings that can change between environments, like database credentials or API keys.

2. Step 2: Differentiate from other files

   Application logic, routes, and user data are handled elsewhere, not in .env.

3. Final Answer:

   To store environment-specific configuration settings outside the code -> Option D

4. Quick Check:

   Environment config = store settings outside code [OK]

Hint: Remember: .env holds settings, not code or data [OK]

Common Mistakes:

• Thinking .env contains code logic
• Confusing .env with database or session storage
• Assuming .env stores user data

2. Which of the following is the correct syntax to access an environment variable named APP_NAME in Laravel code?

easy

A. env('APP_NAME')

B. config('APP_NAME')

C. getenv('APP_NAME')

D. $_ENV['APP_NAME']

Solution

1. Step 1: Identify Laravel's helper function for env variables

   Laravel provides the env() helper to access environment variables directly.

2. Step 2: Compare other options

   config() accesses config files, getenv() is PHP native but less used in Laravel, and $_ENV is a PHP superglobal but not recommended.

3. Final Answer:

   env('APP_NAME') -> Option A

4. Quick Check:

   Use env() helper for .env variables [OK]

Hint: Use env('KEY') to get .env values in Laravel [OK]

Common Mistakes:

• Using config() instead of env() for .env variables
• Using PHP native getenv() without Laravel context
• Trying to access $_ENV directly

3. Given the following .env content:

APP_DEBUG=true
APP_NAME=MyApp

What will be the output of this Laravel code?

echo env('APP_DEBUG') ? 'Debug is ON' : 'Debug is OFF';

medium

A. Debug is ON

B. Debug is OFF

C. true

D. false

Solution

1. Step 1: Understand env() returns string values

   The env('APP_DEBUG') returns the string "true" from the .env file, which is truthy in PHP.

2. Step 2: Evaluate the ternary condition

   Since "true" as a string is truthy, the condition is true, so it echoes 'Debug is ON'.

3. Final Answer:

   Debug is ON -> Option A

4. Quick Check:

   env('APP_DEBUG') = 'true' (truthy) [OK]

Hint: env() returns strings; 'true' string is truthy in PHP [OK]

Common Mistakes:

• Assuming env('APP_DEBUG') returns boolean true
• Expecting 'Debug is OFF' because of string type
• Confusing string 'true' with boolean false

4. You wrote this code to get the database host:

$dbHost = env('DB_HOST', 'localhost');

But it always returns 'localhost' even though DB_HOST is set in .env. What is the most likely cause?

medium

A. The env() function does not accept default values

B. Laravel caches config and needs cache cleared

C. The DB_HOST key is misspelled in the code

D. The .env file is missing or not loaded properly

Solution

1. Step 1: Understand Laravel config caching behavior

   Laravel caches configuration for performance. If config cache is not cleared after changing .env, env() may return old values or defaults.

2. Step 2: Identify the fix

   Running php artisan config:clear clears the cache and loads updated .env values.

3. Final Answer:

   Laravel caches config and needs cache cleared -> Option B

4. Quick Check:

   Clear config cache to update env() values [OK]

Hint: Clear config cache after .env changes with artisan command [OK]

Common Mistakes:

• Assuming env() ignores default values
• Not clearing config cache after .env edits
• Misspelling env key without checking

5. You want to set a default timezone in your Laravel app using environment variables. You add APP_TIMEZONE=Europe/Paris to your .env file. How should you correctly apply this setting in config/app.php so the app uses the env value but falls back to 'UTC' if missing?

hard

A. 'timezone' => getenv('APP_TIMEZONE') ?: 'UTC',

B. 'timezone' => config('APP_TIMEZONE', 'UTC'),

C. 'timezone' => env('APP_TIMEZONE', 'UTC'),

D. 'timezone' => 'APP_TIMEZONE' ?? 'UTC',

Solution

1. Step 1: Use env() with default in config file

   In config/app.php, use env('APP_TIMEZONE', 'UTC') to get the env value or fallback to 'UTC'.

2. Step 2: Understand why other options are incorrect

   config() reads config files, not env variables; getenv() is less preferred; and 'APP_TIMEZONE' ?? 'UTC' is a string literal, not a variable.

3. Final Answer:

   'timezone' => env('APP_TIMEZONE', 'UTC'), -> Option C

4. Quick Check:

   Use env() with default in config files [OK]

Hint: In config, use env('KEY', 'default') for env with fallback [OK]

Common Mistakes:

• Using config() instead of env() for .env values
• Using string literals instead of env() calls
• Using getenv() which is less Laravel idiomatic