APP_NAME="MyApp" APP_ENV=local APP_DEBUG=true APP_URL=http://localhost DB_CONNECTION=mysql DB_HOST=127.0.0.1 DB_DATABASE=homestead DB_USERNAME=root DB_PASSWORD=secret MAIL_MAILER=smtp MAIL_HOST=smtp.mailtrap.io
Are you using any specific services like or Laravel Forge ? Share public link
✅ by running php artisan config:cache .
APP_NAME="My Awesome App" APP_ENV=local APP_DEBUG=true APP_URL=http://localhost .env.laravel
Think of it as a set of keys and values, where each key represents a configuration setting, and each value is the actual setting for that environment. For example, you might have a DB_DATABASE key that holds the name of your database, and its value will differ depending on whether you're on your local machine ( myapp_local ), a staging server ( myapp_staging ), or the live production environment ( myapp_production ).
Yes. Laravel's env:encrypt command allows you to safely commit an encrypted .env.encrypted file to version control. Only those with the decryption key can access the original values. This is a secure way to share environment configuration across a team or through CI/CD pipelines.
Then, inside your controllers or services, use the config() helper to access the value: $dbHost = config('database.connections.mysql.host'); Use code with caution. For example, you might have a DB_DATABASE key
APP_NAME=Laravel APP_ENV=local APP_KEY=base64:your_generated_key_here APP_DEBUG=true APP_URL=http://localhost LOG_CHANNEL=stack LOG_DEPRECATIONS_CHANNEL=null LOG_LEVEL=debug DB_CONNECTION=mysql DB_HOST=127.0.0.1 DB_PORT=3306 DB_DATABASE=laravel DB_USERNAME=root DB_PASSWORD= BROADCAST_CONNECTION=log CACHE_STORE=database FILESYSTEM_DISK=local QUEUE_CONNECTION=sync SESSION_DRIVER=database SESSION_LIFETIME=120 MEMCACHED_HOST=127.0.0.1 REDIS_HOST=127.0.0.1 REDIS_PASSWORD=null REDIS_PORT=6379 MAIL_MAILER=smtp MAIL_HOST=mailpit MAIL_PORT=1025 MAIL_USERNAME=null MAIL_PASSWORD=null MAIL_ENCRYPTION=null MAIL_FROM_ADDRESS="hello@example.com" MAIL_FROM_NAME="$APP_NAME" AWS_ACCESS_KEY_ID= AWS_SECRET_ACCESS_KEY= AWS_DEFAULT_REGION=us-east-1 AWS_BUCKET= AWS_USE_PATH_STYLE_ENDPOINT=false PUSHER_APP_ID= PUSHER_APP_KEY= PUSHER_APP_SECRET= PUSHER_HOST= PUSHER_PORT=443 PUSHER_SCHEME=https PUSHER_APP_CLUSTER=mt1 VITE_APP_NAME="$APP_NAME" VITE_PUSHER_APP_KEY="$PUSHER_APP_KEY" VITE_PUSHER_APP_HOST="$PUSHER_HOST" VITE_PUSHER_APP_SCHEME="$PUSHER_SCHEME" VITE_PUSHER_APP_CLUSTER="$PUSHER_APP_CLUSTER" Use code with caution. 2. .env vs. .env.example
: Defines the environment state ( local , staging , production ).
: The current environment (e.g., local , staging , production ). Only those with the decryption key can access
$apiKey = env('API_KEY'); $apiSecret = env('API_SECRET');
This approach ensures that:
