To set up environment variables in Laravel, define them in the .env file using key-value pairs, access them via the env() helper or config files, and avoid hardcoding sensitive data. 1. Define variables like APP_NAME=Laravel in .env (do not commit this file). 2. Use env('APP_NAME', 'DefaultName') in code to retrieve values with a fallback. 3. Load variables into config files (e.g., config/app.php) for better production performance. 4. Reference variables in configuration files such as config/database.php using env() calls. 5. Maintain separate .env files per environment (local, staging, production). 6. Store secrets like API keys in .env and ensure it’s in .gitignore. 7. Clear config and cache after changes with php artisan config:clear and php artisan cache:clear. 8. Update .env.example to guide team members on required variables.

Setting up environment variables in a Laravel app is pretty straightforward, but it’s one of those things that can trip you up if you miss a small detail. The main file you’ll work with is .env, and Laravel makes it easy to access those values throughout your app.

Understanding the .env File

Laravel uses the DotEnv PHP library under the hood, which means your .env file should follow a basic key-value format:

APP_NAME=Laravel
APP_ENV=local
APP_KEY=base64:yourkeyhere

Each line defines an environment variable. You shouldn’t commit this file to version control — instead, share a .env.example file so others know what variables are needed.

Also, after making changes to .env, always run:

• php artisan config:clear
• php artisan cache:clear

Sometimes Laravel caches old values, especially on production servers.

Accessing Variables in Your Application

To use these values in your code, Laravel provides the env() helper function:

$appName = env('APP_NAME', 'DefaultName');

The second parameter is a default value if the key isn't found.

You can also use the config() helper once you define them in config files. For example, in config/app.php:

'name' => env('APP_NAME', 'MyApp'),

Then access it like:

config('app.name');

This method is better for performance in production since Laravel caches config files.

Using Environment Variables in Configuration Files

As mentioned, you'll often see environment variables pulled into configuration files like config/database.php or config/mail.php. This keeps your sensitive data out of those files and makes your app more portable.

For example, your database connection might look like this in config/database.php:

'mysql' => [
    'driver' => 'mysql',
    'host' => env('DB_HOST', '127.0.0.1'),
    'port' => env('DB_PORT', '3306'),
    'database' => env('DB_DATABASE', 'forge'),
    'username' => env('DB_USERNAME', 'forge'),
    'password' => env('DB_PASSWORD', ''),
],

If you're deploying to different environments (local, staging, production), you can have different .env files for each, and Laravel will adapt accordingly.

Handling Sensitive Data

Never store secrets like API keys or passwords directly in your codebase. Use .env for that:

STRIPE_SECRET_KEY=sk_test_XXXXXXXXXX

Also, make sure your .env file is listed in .gitignore. Laravel includes this by default, but double-check if you're setting up a new project.

If you're using something like Vapor or Forge, they handle environment variables differently — sometimes through UI settings or deployment scripts — so don’t always expect a .env file on the server.

That's basically it. It's not complicated, but it's crucial to get right, especially when moving between environments or working in teams. Keep your .env.example updated, clear config caches when needed, and avoid hardcoding values elsewhere.

The above is the detailed content of Configuring environment variables in a Laravel application. For more information, please follow other related articles on the PHP Chinese website!