Stratus uses aDocumentation Index
Fetch the complete documentation index at: https://mintlify.com/AlexanderDamont1/Stratus/llms.txt
Use this file to discover all available pages before exploring further.
.env file at the project root to manage all environment-specific configuration. This file is never committed to version control and must be created on each machine or server where Stratus runs.
Creating the .env file
The repository ships with a.env.example template. Copy it to create your local configuration:
APP_KEY. Without this key, encrypted values (including sessions and cookies) cannot be decrypted.
Application variables
These variables control the core identity and behaviour of the application.| Variable | Description |
|---|---|
APP_NAME | Display name used in notifications and emails. Change to your application’s name. |
APP_ENV | Current environment: local, staging, or production. |
APP_KEY | Encryption key. Generate with php artisan key:generate. |
APP_DEBUG | Set to false in production to suppress stack traces. |
APP_URL | Full base URL including scheme. Used for link generation. |
APP_LOCALE | Default locale for translations (default: en). |
APP_FALLBACK_LOCALE | Fallback locale if translation is missing (default: en). |
APP_FAKER_LOCALE | Locale used by Faker in factories and tests (default: en_US). |
APP_MAINTENANCE_DRIVER | How maintenance mode is tracked — file (default) or database. |
BCRYPT_ROUNDS | Number of bcrypt hashing rounds for passwords (default: 12). Higher values are slower but more secure. |
Database configuration
See Database setup for the full guide. The key variables are:Mail configuration
Mail is required for features such as email verification and password reset.MAIL_MAILER=log writes all outgoing mail to the Laravel log file (storage/logs/laravel.log). This is safe for local development — no emails are sent to real inboxes. For production, configure an SMTP provider.
Example: sending via SMTP (e.g. Mailgun, SES, Postmark)
Example: sending via SMTP (e.g. Mailgun, SES, Postmark)
Example: Mailpit for local development
Example: Mailpit for local development
Mailpit is a local mail catcher bundled with Laravel Sail. Configure it to capture emails in a web UI without sending them:
Session configuration
SESSION_DRIVER=database stores sessions in the sessions table, which is created by the default migrations. This is the default and works reliably on single-server and multi-server setups alike.
| Variable | Description |
|---|---|
SESSION_DRIVER | Where sessions are stored: database (default), file, cookie, redis, memcached. |
SESSION_LIFETIME | Minutes of inactivity before a session expires (default: 120). |
SESSION_ENCRYPT | Encrypt session payloads at rest (default: false). |
SESSION_PATH | Cookie path scope (default: /). |
SESSION_DOMAIN | Cookie domain scope (default: null, uses current host). |
The
database driver requires the sessions table to exist. Run php artisan migrate before starting the application.Queue configuration
| Value | Behaviour |
|---|---|
database | Jobs are queued in the jobs table and processed by a queue worker. This is the default. |
sync | Jobs run immediately in the same process. No worker needed. Useful for simple local setups. |
database (the default), run the queue worker with:
Cache configuration
database cache driver stores cached data in the cache table created by migrations. No additional services are required.
| Value | Description |
|---|---|
database | Cache stored in the cache table (default). |
file | Cache stored in storage/framework/cache. |
redis | Recommended for high-traffic production environments. |
memcached | High-performance in-memory cache. Requires MEMCACHED_HOST. |
Redis configuration
Redis can be used as a driver for sessions, cache, and queues. Configure the connection with:Frontend
VITE_APP_NAME exposes the application name to Vite and the JavaScript frontend. Variables prefixed with VITE_ are the only .env values accessible in browser-side JavaScript.
Logging
LOG_LEVEL=error or LOG_LEVEL=warning in production to reduce log volume. Available levels follow RFC 5424: debug, info, notice, warning, error, critical, alert, emergency.