Laravel本地应用上线生产环境：除已列步骤外还需哪些操作？

Great question! You’ve already nailed some foundational steps for moving your Laravel app from development to production, but there are several more security, performance, and reliability-focused tasks to complete before going live. Let’s dive into them:

Security Enhancements #

• Generate a unique production APP_KEY
  Never reuse your development APP_KEY in production. Run this command to generate a fresh, secure key (the --force flag ensures it overwrites the existing one in your production .env):
  php artisan key:generate --force
• Lock down database permissions
  Use a dedicated database user for your app with minimum necessary permissions (e.g., only SELECT, INSERT, UPDATE, DELETE—avoid granting DROP or CREATE). Update your .env with production-specific database credentials, and never use your local/dev database user in production.
• Secure the .env file
  This file contains sensitive data (API keys, database passwords), so set strict file permissions on your server:
  chmod 600 .env
  Double-check that .env is included in your .gitignore to prevent accidental commits to version control.
• Enforce HTTPS everywhere
  Set APP_URL=https://your-domain.com in .env, then configure your web server (Nginx/Apache) to redirect all HTTP traffic to HTTPS. Use a trusted SSL certificate (Let’s Encrypt offers free, valid certificates) to encrypt data in transit.
• Clean up development dependencies
  Install only production-ready packages with:
  composer install --no-dev --optimize-autoloader
  This removes dev tools like PHPUnit or Dusk and optimizes the autoloader for better performance. Run composer audit regularly to check for vulnerable dependencies.

Performance Optimizations #

• Cache configuration and routes
  Speed up request handling by caching your app’s config and routes:
  php artisan config:cache
php artisan route:cache
  Note: You’ll need to re-run these commands anytime you modify config files or routes in production.
• Precompile Blade views
  Eliminate runtime Blade compilation overhead with:
  php artisan view:cache
• Switch to a high-performance cache driver
  Replace the default file cache driver with Redis or Memcached (update CACHE_DRIVER=redis in .env). These in-memory stores drastically improve cache read/write speeds.
• Set up a queue system for background tasks
  Offload slow tasks (like sending emails, processing uploads) to a queue. Configure your queue driver (e.g., Redis, Database) in .env, then use Supervisor to keep queue workers running continuously:
  php artisan queue:work --daemon
• Optimize frontend assets
  Compress and hash your JS/CSS files using your build tool:
  • For Vite: npm run build
  • For Laravel Mix: npm run production
    Configure your web server to set long cache headers for these hashed assets to reduce repeat downloads.

Reliability & Maintenance #

• Implement automated backups
  Back up your database and app files regularly. Use tools like mysqldump for databases, or packages like spatie/laravel-backup to automate backups to cloud storage (S3, Google Drive)—never store backups only on your production server.
• Set up error monitoring
  Beyond enabling logs, use tools like Sentry or Laravel Telescope (restrict access to admins only) to track and alert you to production errors in real time. This helps you fix issues before users notice.
• Configure proper logging
  In config/logging.php, set up daily log rotation to prevent oversized log files. You can also configure centralized logging (e.g., with Papertrail) to aggregate logs from multiple servers.
• Test in a staging environment first
  Replicate your production setup in a staging server and test all critical workflows (user auth, payments, form submissions) thoroughly. Run performance tests (e.g., with ab or JMeter) to ensure your server can handle expected traffic.
• Update environment-specific services
  Swap out development services for production-grade ones:
  • Use a professional SMTP provider (SendGrid, Mailgun) instead of local mail servers.
  • Switch to cloud file storage (S3, DigitalOcean Spaces) instead of local storage if your app handles uploads.

By covering these steps, you’ll ensure your Laravel app is secure, fast, and reliable when it goes live. Always have a rollback plan ready (e.g., a backup of your previous deployment) in case you need to revert quickly.

内容的提问来源于stack exchange，提问作者Istiaque Ahmed