How do you deploy and optimize Laravel for production?

Question

Accepted Answer

Deploying Laravel to production involves a sequence of **optimization commands** (caching config/routes/views), secure configuration, running a proper web server stack, and managing queues and the scheduler. Laravel provides specific Artisan commands to optimize for production.

## The production optimization commands

```bash
# cache config, routes, and views → significant speedup (skip recompilation per request)
php artisan config:cache        # merge & cache all config into one file
php artisan route:cache          # cache compiled routes
php artisan view:cache           # precompile Blade templates
php artisan event:cache
# or all at once:
php artisan optimize

composer install --optimize-autoloader --no-dev    # optimized autoloader, no dev deps
```

These caching commands are **essential for production performance** — they precompute config, routes, and views so PHP doesn't reparse/recompile them on every request, a meaningful speedup. (Note: after config caching, `env()` only works in config files — code must read via `config()`.)

## Secure production configuration

```bash
# .env (production)
APP_ENV=production
APP_DEBUG=false          # ❗ MUST be false — debug=true leaks sensitive info/stack traces
APP_KEY=...               # generated, kept secret
```

```text
✓ APP_DEBUG=false (leaking debug info is a serious security risk)
✓ Keep secrets in .env (gitignored) / environment; never commit them
✓ Use HTTPS; set secure session/cookie settings
```

## The server stack and supporting processes

```text
✓ Web server: NGINX + PHP-FPM (the standard PHP production stack)
✓ Database: a real DB (MySQL/PostgreSQL) with migrations run on deploy (php artisan migrate)
✓ Queue workers: run via Supervisor (or Laravel Horizon for Redis) — keep them alive
✓ Scheduler: ONE cron entry running `schedule:run` every minute
✓ Cache/sessions: Redis (shared, fast) — especially for multi-server, keep app STATELESS
✓ Use OPcache (PHP bytecode cache) — a major PHP-level speedup
```

## Managed deployment options

```text
Laravel Forge (server provisioning), Vapor (serverless on AWS), or platforms
(Envoyer for zero-downtime deploys) automate much of this.
```

## Why it matters

Deploying and optimizing Laravel for production is essential knowledge for taking applications live correctly, securely, and performantly — and it involves Laravel-specific steps that differ from development.

The **production optimization commands** are particularly important and often overlooked: `config:cache`, `route:cache`, `view:cache` (or `optimize`) precompute configuration, routes, and templates so PHP doesn't reparse them on every request, providing a meaningful, essential performance boost — failing to run these in production leaves significant performance on the table.

Several aspects are also security-critical: **`APP_DEBUG=false`** is mandatory (debug mode leaks sensitive stack traces and configuration to attackers — a serious vulnerability), secrets must stay out of version control, and HTTPS/secure sessions are required.

Understanding the proper **server stack** (NGINX + PHP-FPM, a real database with migrations run on deploy, OPcache for PHP-level speed) and the **supporting processes** (queue workers kept alive via Supervisor/Horizon, the scheduler's single cron entry, Redis for shared cache/sessions especially in multi-server stateless setups) is necessary for a working, performant production deployment.

Knowing managed options (Forge, Vapor, Envoyer for zero-downtime deploys) is also valuable.

Since every real Laravel application must be deployed correctly to be fast and secure — and since deployment mistakes (skipping optimization caches, leaving debug on, mishandling queues/scheduler) cause real performance and security problems — understanding Laravel's production deployment and optimization (the caching commands, secure config, server stack, and supporting processes) is important senior-level knowledge for shipping production-ready applications, a frequently-relevant, professionally-essential topic.