{"id":451,"date":"2025-08-27T22:10:26","date_gmt":"2025-08-27T22:10:26","guid":{"rendered":"https:\/\/1v0.net\/blog\/?p=451"},"modified":"2025-08-27T22:28:31","modified_gmt":"2025-08-27T22:28:31","slug":"laravel-nginx-best-practices-for-production","status":"publish","type":"post","link":"https:\/\/1v0.net\/blog\/laravel-nginx-best-practices-for-production\/","title":{"rendered":"Laravel & Nginx: Best Practices for Production"},"content":{"rendered":"\n

Laravel & Nginx: Best Practices for Production<\/strong><\/h2>\n\n\n\n

Caddy<\/strong> might be the new kid on the block, but Nginx<\/strong> remains the most widely used web server for Laravel in production. It\u2019s stable, efficient, and battle-tested at scale. To run a Laravel 12 application smoothly in production with Nginx, you\u2019ll need the right configuration, caching rules, and security headers. In this guide, we\u2019ll walk through best practices to deploy Laravel with Nginx.<\/p>\n\n\n\n

<\/div>\n\n\n\n

1 \u2014 Install Nginx & PHP-FPM<\/strong><\/h2>\n\n\n\n

Most Linux servers don\u2019t ship with Nginx preinstalled. You\u2019ll need Nginx plus PHP-FPM to handle dynamic PHP requests efficiently.<\/p>\n\n\n

sudo apt update\nsudo apt install -y nginx php8.3-fpm php8.3-mysql unzip curl<\/code><\/span>Code language:<\/span> Bash<\/span> (<\/span>bash<\/span>)<\/span><\/small><\/pre>\n\n\n
We install the nginx<\/code> server, PHP 8.3 FPM for executing Laravel, and supporting packages. If you\u2019re deploying on a provider like DigitalOcean or AWS, see How to Deploy a Laravel 12 App on DigitalOcean<\/a> and Deploying Laravel on AWS: Complete Guide (2025)<\/a> for cloud-specific steps.<\/p>\n\n\n\n
<\/div>\n\n\n\n
2 \u2014 Nginx Server Block for Laravel<\/strong><\/h2>\n\n\n\n
Create a new config file \/etc\/nginx\/sites-available\/laravel.conf<\/code> and point it to the public\/<\/code> directory. This ensures only public assets are directly accessible.<\/p>\n\n\n
server<\/span> {\n    listen<\/span> 80<\/span>;\n    server_name<\/span> your-domain.com;\n    root<\/span> \/var\/www\/current\/public;\n\n    index<\/span> index.php index.html;\n\n    location<\/span> \/ {\n        try_files<\/span> $uri<\/span> $uri<\/span>\/ \/index.php?$query_string<\/span>;\n    }\n\n    location<\/span> ~ \\.php$<\/span> {\n        include<\/span> fastcgi_params;\n        fastcgi_pass<\/span> unix:\/var\/run\/php\/php8.3-fpm.sock;\n        fastcgi_param<\/span> SCRIPT_FILENAME $realpath_root<\/span>$fastcgi_script_name<\/span>;\n        include<\/span> fastcgi_params;\n    }\n\n    location<\/span> ~ \/\\.ht<\/span> {\n        deny<\/span> all;\n    }\n}<\/code><\/span>Code language:<\/span> Nginx<\/span> (<\/span>nginx<\/span>)<\/span><\/small><\/pre>\n\n\n
Here, root<\/code> points to public\/<\/code>, and all requests fall back to index.php<\/code> if no file is found. The fastcgi_pass<\/code> points to the PHP-FPM socket (adjust version accordingly).<\/p>\n\n\n\n
<\/div>\n\n\n\n
3 \u2014 Enable Compression<\/strong><\/h2>\n\n\n\n
Gzip (or Brotli if supported) should be enabled to reduce file sizes. Add this to your nginx.conf<\/code> under the http<\/code> block.<\/p>\n\n\n
gzip<\/span> on<\/span>;\ngzip_comp_level<\/span> 5<\/span>;\ngzip_min_length<\/span> 1024<\/span>;\ngzip_proxied<\/span> any;\ngzip_types<\/span> text\/plain text\/css application\/javascript application\/json application\/xml image\/svg+xml;\ngzip_vary<\/span> on<\/span>;<\/code><\/span>Code language:<\/span> Nginx<\/span> (<\/span>nginx<\/span>)<\/span><\/small><\/pre>\n\n\n
<\/div>\n\n\n\n
4 \u2014 Handling HTTPS<\/strong><\/h2>\n\n\n\n
Use Let\u2019s Encrypt certificates or integrate with your hosting provider\u2019s SSL. With Nginx, configure your server<\/code> block for HTTPS:<\/p>\n\n\n
server<\/span> {\n    listen<\/span> 443<\/span> ssl http2;\n    server_name<\/span> your-domain.com;\n\n    ssl_certificate<\/span> \/etc\/letsencrypt\/live\/your-domain.com\/fullchain.pem;\n    ssl_certificate_key<\/span> \/etc\/letsencrypt\/live\/your-domain.com\/privkey.pem;\n\n    include<\/span> snippets\/ssl-params.conf;\n\n    root<\/span> \/var\/www\/current\/public;\n    index<\/span> index.php index.html;\n\n    location<\/span> \/ {\n        try_files<\/span> $uri<\/span> $uri<\/span>\/ \/index.php?$query_string<\/span>;\n    }\n}<\/code><\/span>Code language:<\/span> Nginx<\/span> (<\/span>nginx<\/span>)<\/span><\/small><\/pre>\n\n\n
<\/div>\n\n\n\n
5 \u2014 Optimize Nginx & PHP-FPM<\/strong><\/h2>\n\n\n\n
Set proper buffer and worker configurations in nginx.conf<\/code> and tune PHP-FPM for concurrent requests.<\/p>\n\n\n
# \/etc\/nginx\/nginx.conf (http { ... })<\/span>\nworker_processes<\/span> auto;\nworker_connections<\/span> 1024<\/span>;\nclient_max_body_size<\/span> 20M<\/span>;\n\n# PHP upstream for TCP (if not using socket)<\/span>\nupstream<\/span> php {\n    server<\/span> 127.0.0.1:9000<\/span>;\n}<\/code><\/span>Code language:<\/span> Nginx<\/span> (<\/span>nginx<\/span>)<\/span><\/small><\/pre>\n\n\n
Here, worker_processes auto;<\/code> lets Nginx use available CPU cores. The client_max_body_size<\/code> ensures large uploads don\u2019t get rejected prematurely.<\/p>\n\n\n
; \/etc\/php\/8.3\/fpm\/pool.d\/www.conf<\/span>\npm<\/span> = dynamic\npm.max_children<\/span> = 20<\/span>\npm.start_servers<\/span> = 4<\/span>\npm.min_spare_servers<\/span> = 4<\/span>\npm.max_spare_servers<\/span> = 8<\/span><\/code><\/span>Code language:<\/span> TOML, also INI<\/span> (<\/span>ini<\/span>)<\/span><\/small><\/pre>\n\n\n
<\/div>\n\n\n\n
6 \u2014 Add a Health Check Route<\/strong><\/h2>\n\n\n\n
Monitoring your Laravel + Nginx deployment ensures uptime. Add a simple route for your load balancer or uptime monitor.<\/p>\n\n\n
\/\/ routes\/web.php<\/span>\nRoute::get('\/health'<\/span>, function<\/span> ()<\/span> <\/span>{\n    return<\/span> response()->json([\n        'status'<\/span> => 'ok'<\/span>,\n        'app'<\/span> => config('app.name'<\/span>),\n        'time'<\/span> => now(),\n    ]);\n});<\/code><\/span>Code language:<\/span> PHP<\/span> (<\/span>php<\/span>)<\/span><\/small><\/pre>\n\n\n
This \/health<\/code> endpoint is lightweight and lets Nginx or a monitoring tool confirm your Laravel app is alive. You can extend it with database or cache checks for better observability.<\/p>\n\n\n\n
<\/div>\n\n\n\n
Wrapping Up<\/h2>\n\n\n\n
Deploying Laravel 12 with Nginx is reliable and production-friendly when configured correctly. Focus on secure server blocks, efficient PHP-FPM tuning, caching, and TLS. For large-scale scenarios, you may want to explore Optimizing Laravel for High Concurrency with Octane<\/a>. If you\u2019re still on shared hosting, revisit How to Deploy Laravel to Shared Hosting (Step by Step)<\/a> to compare approaches.<\/p>\n\n\n\n
<\/div>\n\n\n\n
What\u2019s Next<\/h2>\n\n\n\n
These PHP-FPM settings control concurrency. Adjust pm.max_children<\/code> based on available memory and expected traffic. For very high traffic, consider Optimizing Laravel for High Concurrency with Octane<\/a>.<\/p>\n\n\n\n
With this, Caddy would have automated TLS by default, but in Nginx you typically configure Let\u2019s Encrypt with certbot<\/code>. If you\u2019re deploying on a cloud provider like AWS, offload TLS termination to an ALB or load balancer (Deploying Laravel on AWS: Complete Guide (2025)<\/a>).<\/p>\n\n\n\n
This ensures text-based assets are compressed before sending to the client, saving bandwidth and improving speed. For further performance tuning, check 10 Proven Ways to Optimize Laravel for High Traffic<\/a>.<\/p>\n\n\n\n