Avalúo Vehicular uses Laravel’sDocumentation Index
Fetch the complete documentation index at: https://mintlify.com/alber1802/AvaluoVehicular/llms.txt
Use this file to discover all available pages before exploring further.
.env file system to manage all environment-specific configuration. Every variable that differs between development, staging, and production — application keys, database paths, mail credentials, and debug flags — lives in this single file, which is intentionally excluded from version control. The canonical template is .env.example, committed to the repository, and lists every variable the application expects with safe placeholder values. Your local .env is derived from it and must never be committed.
Initial Setup
After cloning the repository, create your local environment file and generate a fresh application key:php artisan key:generate writes a cryptographically secure random value into APP_KEY. Without it, encrypted cookies, sessions, and queue payloads cannot be decrypted and the application will throw runtime errors.
The
APP_KEY value must never be committed to version control. It is the master secret used to encrypt all application data. If it changes in production, all existing encrypted sessions and payloads will be invalidated. Rotate it only intentionally, never accidentally.Variable Reference
App
The human-readable name of the application. Displayed in email notifications and used as the
VITE_APP_NAME alias in the React frontend. Set to "Avaluo Vehicular" in production.The application environment. Accepted values are
local, staging, and production. Controls which service providers and behaviours are active. Laravel uses this to determine whether to optimize configs and routes.The 32-character base64-encoded encryption key. Generated by
php artisan key:generate. Required for all encrypted data including sessions, cookies, and password reset tokens.When
true, Laravel renders detailed exception pages with full stack traces and environment context in the browser. Set to false in every environment that is reachable by end-users.The fully-qualified base URL of the application, including the scheme. Used to generate absolute URLs in emails, password-reset links, and asset paths. In the Docker production configuration this is set to
http://127.0.0.1:8080.The default language for translations and date formatting. Set to
es in the Docker production configuration to match the Spanish-language interface of Avalúo Vehicular. Also governs APP_FALLBACK_LOCALE and APP_FAKER_LOCALE.Logging
The logging channel to use.
stack aggregates multiple channels defined in config/logging.php. Other options include single, daily, syslog, and errorlog.The minimum severity level for log entries. Follows RFC 5424:
debug, info, notice, warning, error, critical, alert, emergency. In the Docker production configuration this is set to error to suppress verbose output.Database
The database driver. Avalúo Vehicular uses
sqlite as its default and production driver — no separate database server is required. See Database Setup for full details.Session
Where session data is persisted. Set to
database, meaning sessions are stored in the sessions table created by the initial migration. This supports the Fortify-based authentication system and allows sessions to be inspected and invalidated from the database.Number of minutes before an idle session expires. After this period of inactivity the user is logged out automatically. The default of
120 minutes (two hours) applies in both development and production.Queue
The queue backend driver. Set to
database, meaning queued jobs are stored in the jobs table. No Redis or external message broker is required. Use php artisan queue:work to process jobs.Cache
The default cache driver. Set to
database, meaning cached data is stored in the cache table. This choice keeps the infrastructure footprint minimal — the same SQLite file handles sessions, cache, and queues simultaneously.The mail transport driver. Use
log in development to write emails to the log file instead of sending them. In the Docker production configuration this is set to resend, using the Resend transactional email API via a RESEND_API_KEY.The SMTP host to connect to when using the
smtp mailer. Only relevant when MAIL_MAILER=smtp.The SMTP port. Common values are
587 (STARTTLS), 465 (SSL), and 2525 (alternative STARTTLS).The SMTP authentication username. Leave
null for local log-only mailers.The SMTP authentication password or API token, depending on the mailer. Leave
null for local log-only mailers.The sender email address used in all outgoing mail. In the Docker production configuration this is
notificaciones@avaluovehicularumsa.life.File Storage
The default filesystem disk for file storage operations. Set to
local, meaning uploaded files are stored under storage/app/. Avalúo Vehicular stores vehicle inspection documents and images through this disk. Change to s3 and configure the AWS_* variables to use S3-compatible object storage.Docker-Specific Variables
The.env.docker file is the production configuration used when running the application in a Docker container. It differs from .env.example in several important ways:
| Variable | Development (.env.example) | Docker Production (.env.docker) |
|---|---|---|
APP_ENV | local | production |
APP_DEBUG | true | false |
APP_URL | http://localhost | http://127.0.0.1:8080 |
APP_LOCALE | en | es |
LOG_LEVEL | debug | error |
DB_DATABASE | (auto-resolved) | /var/www/html/database/database.sqlite |
MAIL_MAILER | log | resend |
MAIL_FROM_ADDRESS | hello@example.com | notificaciones@avaluovehicularumsa.life |
When deploying with Docker, copy
.env.docker to .env inside the container image and replace all placeholder values — especially APP_KEY and RESEND_API_KEY — with real secrets injected via Docker secrets or environment variable overrides in your docker-compose.yml.