Deploying a Laravel Application to Cloud Server: Complete Guide

Moving your Laravel application from development to production requires proper server configuration and security settings. The Laravel deploy process involves setting up Nginx, PHP-FPM, queue workers, scheduler, and SSL certificates — each directly impacting your application's performance and security. This guide walks through every step of making a Laravel application production-ready on a cloud server.

Server Preparation and Requirements

Laravel 11 requires PHP 8.2 minimum, Composer, Nginx or Apache, MySQL/PostgreSQL, and Redis (optional). Choose Ubuntu 22.04 LTS on Hosted Cloud cloud servers.

Component	Minimum Version	Recommended
PHP	8.2	8.3 (OPcache enabled)
Nginx	1.18	1.24+
MySQL	8.0	8.0+ (InnoDB)
Redis	6.0	7.0+ (cache + session)
RAM	1 GB	2 GB+ (with queue workers)

Nginx and PHP-FPM Configuration

Nginx uses Laravel's public directory as root and routes all requests to index.php. Calculate the pm.max_children value in PHP-FPM pool settings based on your server's RAM capacity — each PHP worker consumes approximately 30-50 MB of RAM.

💡 Tip: Enable OPcache to prevent PHP files from being recompiled on every request. Set opcache.validate_timestamps=0 in production for maximum performance; run php artisan optimize:clear after each deploy.

Queue Workers and Task Scheduler

Manage Laravel queue workers with Supervisor, which automatically restarts worker processes if they crash. For the task scheduler, add a single crontab entry: * * * * * php /var/www/app/artisan schedule:run. Our Node.js production guide covers similar process management approaches.

⚠️ Important: Always set APP_DEBUG=false and APP_ENV=production in production. Leaving debug mode on exposes sensitive information (database passwords, API keys) to users.

SSL Certificate and Security Settings

Get a free SSL certificate with Let's Encrypt and configure auto-renewal with Certbot. Add HSTS headers in Nginx, enforce TLS 1.2+, and configure security headers (X-Frame-Options, X-Content-Type-Options, CSP). The Let's Encrypt documentation provides detailed setup instructions.

Zero-Downtime Deployment

Set up zero-downtime deployment with Envoy, Deployer, or GitHub Actions. Use symlink-based release management to prepare the new version, run migrations, and switch the symlink for instant cutover. Our CI/CD pipeline guide details the automated deployment process. The official Laravel deployment documentation is also a useful reference.

Frequently Asked Questions

How much RAM does Laravel need?

A basic Laravel application runs fine with 1 GB RAM. If queue workers, Redis, and the database run on the same server, 2 GB minimum is recommended. For heavy traffic, choose 4 GB or more.

Can Laravel run on shared hosting?

Technically possible but not recommended. SSH access, Composer, queue worker, and cron job limitations make VPS or cloud servers the better choice.

Are tools like Laravel Forge or Ploi necessary?

These tools simplify server management but are not required. Manual setup gives you full control over server configuration and saves on subscription costs.

Conclusion

A successful Laravel deploy process requires proper server preparation, optimized Nginx and PHP-FPM configuration, Supervisor-managed queue workers, and SSL security layers. Set up zero-downtime deployment to keep user experience uninterrupted.

Cloud Server for Your Laravel Application

Run your Laravel application with NVMe SSD, full root access, and 24/7 technical support.

Explore Cloud Server Plans →