Instead of committing .env , commit a .env.example file that contains all the keys but . C. Protect via Server Configuration
Run the following command to clear the config cache: php artisan config:clear Use code with caution. Or, to clear it and cache the new settings: php artisan config:cache Use code with caution. 7. Using Multiple Environments .env.laravel
A fresh Laravel installation includes a .env.example file. When you start working, you create a copy of this file and rename it to .env . Instead of committing
Note: The second argument is the default value if the key does not exist. $dbPassword = env('DB_PASSWORD'); Use code with caution. 5. Security Best Practices for .env (Crucial) Or, to clear it and cache the new
Since the .env file contains sensitive information, it must be handled with extreme care. A. Never Commit .env to Git
Your .env file should never, ever be committed to version control. Add it to your .gitignore file immediately. # .gitignore file .env B. Use .env.example