Skip to main content
All configuration is managed through the .env file in the project root. Copy .env.example to .env and update the values for your environment.

App settings

Core application identity and runtime behaviour.
Never set APP_DEBUG=true or APP_ENV=local on a production server. Doing so exposes stack traces and environment variables to end users.

Logging

Database

To use SQLite instead of MySQL, set DB_CONNECTION=sqlite and DB_DATABASE to the absolute path of your .sqlite file, for example /absolute/path/to/database/database.sqlite. The DB_HOST, DB_PORT, DB_USERNAME, and DB_PASSWORD variables are ignored for SQLite.

Session

Cache and queue

Redis

Required only when CACHE_STORE, SESSION_DRIVER, or QUEUE_CONNECTION is set to redis.

Mail

The default mailer is log, which writes emails to the Laravel log file instead of sending them. This is suitable for local development.
During local development, keep MAIL_MAILER=log to avoid accidental email delivery. Inspect sent emails in storage/logs/laravel.log.

AWS / S3

Required only when FILESYSTEM_DISK=s3.

Memcached

Required only when CACHE_STORE=memcached.

Front-end

This project uses Laravel Mix (Webpack) as its asset bundler, not Vite. The VITE_APP_NAME variable is present in .env.example because it is part of the default Laravel 11 skeleton, but it has no effect on the compiled assets. Front-end environment variables are not currently used in the build configuration (webpack.mix.js).