Скачать или смотреть Serving Your Laravel App Alongside Legacy PHP Files with Nginx

Learn how to configure Nginx to serve a Laravel application from a subdirectory while also handling legacy PHP files from another directory.
---
This video is based on the question https://stackoverflow.com/q/62917028/ asked by the user 'realtebo' ( https://stackoverflow.com/u/1055279/ ) and on the answer https://stackoverflow.com/a/62917272/ provided by the user 'Daniel W.' ( https://stackoverflow.com/u/1948292/ ) at 'Stack Overflow' website. Thanks to these great users and Stackexchange community for their contributions.

Visit these links for original content and any more details, such as alternate solutions, latest updates/developments on topic, comments, revision history etc. For example, the original title of the Question was: Laravel + Nginx: can we serve app from /something and from a different folder?

Also, Content (except music) licensed under CC BY-SA https://meta.stackexchange.com/help/l...
The original Question post is licensed under the 'CC BY-SA 4.0' ( https://creativecommons.org/licenses/... ) license, and the original Answer post is licensed under the 'CC BY-SA 4.0' ( https://creativecommons.org/licenses/... ) license.

If anything seems off to you, please feel free to write me at vlogize [AT] gmail [DOT] com.
---
Serving Your Laravel App Alongside Legacy PHP Files with Nginx: A Step-by-Step Guide

In web development, servers play a crucial role in how applications are accessed and served to users. A common scenario many developers face is the need to serve multiple applications from the same domain. For example, you might have a legacy PHP application that is older and lacks modern URL handling capabilities, but you also want to run a fresh Laravel application. The challenge is to serve both applications seamlessly in a manner that does not disrupt user experience.

Understanding the Problem

Imagine the following structure on your server:

/var/www/mainapp – Contains legacy PHP files that do not utilize modern routing.

/var/www/laravel – Contains your Laravel application.

You want to achieve the following URL structure:

Accessing domain.tld should load the legacy application.

Accessing domain.tld/laravel should load the Laravel application, along with all its subroutes.

However, you may run into issues since Laravel applications typically serve all traffic through the public/index.php file, making it challenging to set up without proper configuration.

Solution Overview

To solve this issue, we can configure Nginx, a popular web server, to handle requests to both applications correctly. The configuration will specify how to direct incoming traffic based on the URL path. Let's break down the steps you need to follow.

Nginx Configuration Steps

Open the Nginx Configuration File
Locate and open your Nginx configuration file, which is usually found at /etc/nginx/sites-available/default or another file if you are using a different server block.

Add the Server Block Configuration
Insert the following configuration into your server block:

[[See Video to Reveal this Text or Code Snippet]]

Breakdown of the Configuration

server_name: This specifies the domain name that this server block will respond to, i.e., domain.tld.

location /: This block serves requests that do not start with /laravel, directing them to the legacy application at /var/www/mainapp.

location /laravel: This block specifically handles requests that start with /laravel, pointing to the public directory of your Laravel application. Here’s what each part does:

alias: Specifies the path to your Laravel public directory.

try_files: This directive attempts to serve the file directly. If it doesn't exist, it redirects the request to Laravel's index.php, which handles routing internally.

PHP Handling: The location ~ .php$ block defines how Nginx should handle PHP requests. Ensure that you adjust the fastcgi_pass line to match your PHP-FPM socket configuration.

Conclusion

With the above Nginx configuration, you have successfully set up your server to serve both a legacy PHP application and a modern Laravel application from a single domain. By segmenting traffic based on the URL structure, users can access each application smoothly without interruption.

This kind of configuration not only improves the efficiency of your web server but also enhances the user experience, allowing you to maintain older applications while progressively adopting newer technologies like Laravel.

Feel free to follow this guide, and don’t hesitate to tweak the configuration to best suit your needs!