How do I set environment variables in Laravel?

The way to set environment variables in Laravel is to use the .env file, store the variables in a hidden file at the root of the project, and access them through the env() function; but to ensure compatibility with the configuration cache, you should use env() in the configuration file and use config() in the application code to call the variables. The specific steps are as follows: 1. Define variables such as APP_DEBUG=true in the .env file; 2. Read variables using env('APP_DEBUG'); 3. Create config/app.php file and reference environment variables; 4. Call them in the application through config('app.debug_mode'); 5. Use php artisan config:cache to enable configuration cache; 6. You can create multiple environment files such as .env.local and .env.production to adapt to different environments; 7. Modify the APP_ENV value in the main .env file to switch the environment. Also be careful not to submit .env files to version control, but add them to .gitignore.

Setting environment variables in Laravel is straightforward, and it's something you'll likely do early on—whether you're connecting to a database, setting up API keys, or managing different app configurations across environments.

Use the .env File

Laravel uses a .env file at the root of your project to store environment variables. When the app runs, these values ​​are loaded into the $_ENV array and can be accessed using the env() helper function.

For example, if you add this line to your .env file:

 APP_DEBUG=true

You can access it like this:

 $debugMode = env('APP_DEBUG');

⚠️ Never commit your .env file to version control—it often contains sensitive information like API keys or database passwords. Make sure it's included in your .gitignore .

Also, there's an .env.example file that comes with a fresh Laravel install. You can use this as a template for others working on your project to know what variables they should set.

Access Variables Using config() instead of env() in Production

While env() is convenient, Laravel actually recommends using the config system in production. Why?

Because when you run php artisan config:cache , Laravel caches all configuration values—but it ignores any calls to env() after that point.

So the better practice is to create a config file (like config/app.php ) and reference the environment variable there:

 // config/app.php
Return [
    'debug_mode' => env('APP_DEBUG', false),
];

Then use it like this:

 config('app.debug_mode');

This way, your variables work properly even when config caching is enabled.

• Always use config() in application code.
• Use env() only inside config files.
• Run php artisan config:clear if you change config files after caching.

Multiple Environment Files

Sometimes you need different settings for local, staging, and production. Laravel supports multiple .env files based on your current environment.

For example:

• .env – default
• .env.local – used when APP_ENV=local
• .env.production – used when APP_ENV=production

To switch environments, update the APP_ENV value in your main .env file:

 APP_ENV=local

Laravel will then load the matching .env.local file if it exists.

This is especially useful on platforms like Forge or Vapor where you might have separate deployment settings per environment.

That's how you manage environment variables in Laravel—set them in .env , reference them through config files, and avoid calling env() directly in your app logic. It keeps things clean, secure, and works well whether you're developing locally or deploying to production.

The above is the detailed content of How do I set environment variables in Laravel?. For more information, please follow other related articles on the PHP Chinese website!