.env file and environment variables in Laravel - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ component_behavior

intermediate

What is the output of this Laravel config call?

Given the .env file contains APP_NAME=MyApp, what will config('app.name') return in a Laravel controller?

Laravel

<?php
// .env file
APP_NAME=MyApp

// In a controller method
return config('app.name');

A "MyApp"

B "APP_NAME"

C null

D "app.name"

💡 Hint

Remember Laravel loads .env values into config files during bootstrap.

The config('app.name') call returns the value set in config/app.php which uses env('APP_NAME', 'Laravel'). Since APP_NAME is set in .env as "MyApp", it returns "MyApp".

📝 Syntax

intermediate

Which .env syntax is correct for setting a boolean?

You want to set APP_DEBUG to true in your .env file. Which line is correct?

A APP_DEBUG=true

B APP_DEBUG=True

C APP_DEBUG=1

D APP_DEBUG='true'

💡 Hint

.env files treat all values as strings; Laravel converts some values automatically.

Laravel treats APP_DEBUG as a boolean. Setting APP_DEBUG=1 works correctly because Laravel converts '1' to true. Other options are strings and may not convert properly.

🔧 Debug

advanced

Why does env('MY_VAR') return null despite being set in .env?

You set MY_VAR=hello in your .env file but env('MY_VAR') returns null in your Laravel app. What is the most likely cause?

A The variable name is case sensitive and should be lowercase

B The .env file is missing the closing semicolon

C You need to restart the web server for .env changes to apply

D You forgot to run <code>php artisan config:cache</code> after changing .env

💡 Hint

Think about Laravel's config caching behavior.

If you have cached your config with php artisan config:cache, Laravel ignores .env changes until you clear or refresh the cache. This causes env() to return null for new variables.

❓ state_output

advanced

What is the value of config('database.default') after this .env change?

If your .env file has DB_CONNECTION=pgsql and your config/database.php uses env('DB_CONNECTION', 'mysql'), what will config('database.default') return?

A "mysql"

B "pgsql"

C null

D "DB_CONNECTION"

💡 Hint

Check how env fallback values work.

The config/database.php file uses env('DB_CONNECTION', 'mysql'). Since DB_CONNECTION is set to "pgsql" in .env, the config returns "pgsql".

🧠 Conceptual

expert

Why should sensitive keys not be committed to version control in .env?

Which is the best reason to exclude .env files containing sensitive keys from version control systems like Git?

A To prevent exposing secrets like API keys and passwords publicly

B To avoid merge conflicts when multiple developers edit the same .env

C Because Laravel automatically regenerates .env files on deployment

D Because .env files are too large and slow down Git operations

💡 Hint

Think about security risks of sharing secrets.

.env files often contain sensitive information like database passwords and API keys. Committing them publicly risks exposing these secrets to unauthorized users.

Practice

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

easy

A. To store environment-specific settings like database credentials and API keys

B. To write the main application logic

C. To define routes for the application

D. To store user session data

Solution

1. Step 1: Understand the role of the .env file

   The .env file holds configuration values that change based on the environment, such as development or production.

2. Step 2: Identify what is stored in .env

   It stores sensitive data like database credentials, API keys, and other settings that should not be hardcoded.

3. Final Answer:

   To store environment-specific settings like database credentials and API keys -> Option A

4. Quick Check:

   .env stores environment settings = B [OK]

Hint: Remember: .env holds secrets and settings outside code [OK]

Common Mistakes:

• Thinking .env contains application logic
• Confusing .env with route files
• Storing user data in .env

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

easy

A. config('APP_NAME')

B. env('APP_NAME')

C. $_ENV['APP_NAME']

D. getenv('APP_NAME')

Solution

1. Step 1: Recall Laravel's helper for environment variables

   Laravel provides the env() helper function to access variables from the .env file.

2. Step 2: Compare options

   config() accesses config files, not .env directly. $_ENV and getenv() are PHP ways but not recommended in Laravel.

3. Final Answer:

   env('APP_NAME') -> Option B

4. Quick Check:

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

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

Common Mistakes:

• Using config() instead of env()
• Trying to access $_ENV directly
• Confusing PHP native functions with Laravel helpers

3. Given the following .env file content:

APP_DEBUG=true
APP_NAME=MyApp

What will be the output of this Laravel code?

if (env('APP_DEBUG')) {
    echo env('APP_NAME');
} else {
    echo 'Debug off';
}

medium

A. null

B. Debug off

C. true

D. MyApp

Solution

1. Step 1: Check the value of APP_DEBUG

   In the .env, APP_DEBUG=true means env('APP_DEBUG') returns true (boolean).

2. Step 2: Evaluate the if condition and output

   Since APP_DEBUG is true, the code echoes env('APP_NAME'), which is "MyApp".

3. Final Answer:

   MyApp -> Option D

4. Quick Check:

   APP_DEBUG=true triggers echo of APP_NAME = A [OK]

Hint: True in .env triggers if-block; echo APP_NAME value [OK]

Common Mistakes:

• Thinking env('APP_DEBUG') returns string 'true' instead of boolean
• Confusing output with 'Debug off'
• Assuming env() returns null if variable exists

4. You added a new variable API_KEY=12345 to your .env file but env('API_KEY') returns null in your Laravel app. What is the most likely cause?

medium

A. You forgot to clear the configuration cache after updating .env

B. The .env file must be renamed to .env.local

C. Laravel does not support custom variables in .env

D. You must restart the web server to read .env changes

Solution

1. Step 1: Understand Laravel config caching

   Laravel caches configuration for performance. Changes in .env won't reflect until cache is cleared.

2. Step 2: Identify the fix

   Running php artisan config:clear clears the cache and allows env() to read new variables.

3. Final Answer:

   You forgot to clear the configuration cache after updating .env -> Option A

4. Quick Check:

   Clear config cache after .env changes = C [OK]

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

Common Mistakes:

• Renaming .env file incorrectly
• Assuming Laravel ignores custom variables
• Restarting server without clearing config cache

5. You want to set a default value for an environment variable MAIL_PORT in Laravel code if it is not set in the .env file. Which of the following is the best way to do this?

hard

A. env('MAIL_PORT') ?? 587

B. env('MAIL_PORT') ?: 587

C. env('MAIL_PORT', 587)

D. config('mail.port', 587)

Solution

1. Step 1: Understand env() default parameter

   The env() helper accepts a second argument as the default value if the variable is missing.

2. Step 2: Compare options for default value

   env('MAIL_PORT', 587) uses env('MAIL_PORT', 587) which is the recommended way. Options A and B rely on PHP operators but can cause issues if the env value is falsy. config('mail.port', 587) accesses config, not .env.

3. Final Answer:

   env('MAIL_PORT', 587) -> Option C

4. Quick Check:

   Use second argument in env() for defaults = D [OK]

Hint: Pass default as second argument to env() [OK]

Common Mistakes:

• Using PHP operators instead of env() default argument
• Accessing config instead of .env directly
• Not providing a default and risking null values