Documentation Index
Fetch the complete documentation index at: https://mintlify.com/MiguelNavas19/miapibcv/llms.txt
Use this file to discover all available pages before exploring further.
Environment Configuration
Mi API BCV uses Laravel’s.env file for configuration. This file is created from .env.example during installation.
Application Settings
Basic Configuration
.env
APP_NAME
Default:Laravel
Description: The application name used in logs and error messages.
Example:
APP_ENV
Default:local
Options: local, development, staging, production
Description: Current environment. Affects error reporting and debugging.
Production:
APP_KEY
Description: Encryption key for sessions and encrypted data. Generated byphp artisan key:generate.
APP_DEBUG
Default:true
Options: true, false
Description: Enable detailed error messages and stack traces.
Production:
APP_URL
Default:http://localhost
Description: Base URL of your application. Used for generating URLs in commands and notifications.
Examples:
Database Configuration
SQLite (Default)
.env
database/database.sqlite
Setup:
MySQL/MariaDB
.env
PostgreSQL
.env
Remote Database
For cloud databases:.env
Use strong passwords and SSL connections for production databases.
Cache Configuration
Database Cache (Default)
.env
cache table. No additional setup required.
File Cache
.env
storage/framework/cache/data/. Good for single-server setups.
Redis Cache
.env
- High-traffic applications
- Multi-server deployments
- Better performance than database cache
Memcached Cache
.env
For production, Redis is recommended over Memcached due to better persistence and features.
Queue Configuration
.env
sync- Process jobs immediately (no queue)database- Store jobs in database (default)redis- Use Redis for queuesqs- Amazon SQS
database is sufficient since the rates:update command runs via scheduler, not queues.
Logging Configuration
.env
LOG_CHANNEL
Options:stack- Multiple channelssingle- Single file logdaily- Daily rotating logssyslog- System logerrorlog- PHP error log
LOG_LEVEL
Options (in order of severity):debug- Detailed debug informationinfo- Informational messagesnotice- Normal but significant eventswarning- Warning messageserror- Error messagescritical- Critical conditionsalert- Action must be taken immediatelyemergency- System is unusable
Session Configuration
.env
SESSION_DRIVER
Options:database- Store in database (default)file- Store in filescookie- Store in cookiesredis- Store in Redis
SESSION_LIFETIME
Default:120 (minutes)
Description: How long sessions remain valid.
Mail Configuration
.env
SMTP Configuration
.env
Popular Providers
Localization
.env
Broadcasting Configuration
.env
log unless you need WebSocket support.
Filesystem Configuration
.env
local- Store instorage/apppublic- Store instorage/app/publics3- Amazon S3
AWS Configuration (Optional)
.env
Production Configuration Example
.env (Production)
Configuration Caching
For better performance in production, cache your configuration:Environment-Specific Settings
Development
Staging
Production
Security Best Practices
Troubleshooting
Configuration changes not taking effect
Configuration changes not taking effect
Clear the configuration cache:
Can't connect to database
Can't connect to database
- Verify credentials in
.env - Test connection:
- Check database server is running
- Verify firewall rules
Cache not working with Redis
Cache not working with Redis
- Verify Redis is running:
redis-cli ping - Check PHP Redis extension:
php -m | grep redis - Test connection in tinker:
Configuration Reference
For advanced configuration, see Laravel’s configuration files inconfig/:
config/app.php- Application settingsconfig/database.php- Database connectionsconfig/cache.php- Cache configurationconfig/queue.php- Queue settingsconfig/mail.php- Email configurationconfig/logging.php- Logging channels
Most settings can be controlled via .env variables without modifying config files.