Configure nginx with multiple locations with different root folders on subdomain

Managing multiple web applications or websites under a single domain or subdomain can be a complex task. Nginx, a powerful and versatile web server, simplifies this process with its flexible configuration options, particularly the ability to define multiple “locations” pointing to different root folders. This allows you to host distinct content for various purposes, such as a main website, a blog, a separate API, or a staging environment, all within the same server block. Mastering this feature is crucial for efficient server management and optimized content delivery.

Understanding Nginx Locations

In Nginx, a “location” block defines how the server should handle requests for specific URIs or parts of your website. These blocks are crucial for directing traffic to the correct files and applications residing in different directories on your server. Each location block operates independently, allowing for granular control over how Nginx processes requests based on the URL structure.

For instance, you might have one location block handling requests for your main website’s static content, another for your blog, and yet another for a specific web application. This modular approach allows you to tailor the server’s behavior depending on the requested resource, optimizing performance and security.

Defining multiple locations with different root folders offers a streamlined way to organize your web server and manage diverse content. It eliminates the need for separate server instances for each application, saving resources and simplifying administration.

Configuring Multiple Locations with Different Roots

Configuring multiple locations with different root folders in Nginx is straightforward. Within your server block, you define each location using the location directive followed by the URI prefix it should match. The root directive within each location block then specifies the corresponding directory from which to serve files.

Here’s a basic example:

server { listen 80; server_name example.com; location / { root /var/www/html/website; index index.html; } location /blog { root /var/www/html/blog; index index.php; } location /api { root /var/www/html/api; index index.py; } } 

This configuration directs requests to example.com to the /var/www/html/website directory, requests to example.com/blog to /var/www/html/blog, and requests to example.com/api to /var/www/html/api. This structure allows you to easily manage different parts of your web presence within a single Nginx configuration.

Handling Subdomains with Different Roots

Extending this concept to subdomains allows for even greater flexibility. You can configure separate server blocks for each subdomain, each with its own set of locations and root folders. This is particularly useful for separating different services or applications while maintaining a unified domain structure.

Consider the following example:

server { listen 80; server_name blog.example.com; root /var/www/html/blog; index index.php; } server { listen 80; server_name api.example.com; root /var/www/html/api; index index.py; } server { listen 80; server_name example.com; root /var/www/html/website; index index.html; } 

This configuration segregates the blog and API onto their own subdomains, simplifying management and allowing for specific configurations for each. This approach improves organization and makes it easier to scale individual services as needed.

Best Practices and Troubleshooting

While configuring multiple locations and subdomains, consider these best practices:

• Prioritize specificity: Nginx processes location blocks from most specific to least specific. Ensure your more specific location blocks are defined before more general ones.
• Use regular expressions cautiously: While powerful, regular expressions in location blocks can be complex and impact performance if not used carefully.

Common troubleshooting steps include:

1. Check Nginx logs: The error log can provide valuable insights into configuration issues.
2. Use a linting tool: This can help identify syntax errors in your configuration file.
3. Test configurations thoroughly: After any changes, ensure your website and applications function as expected.

Optimizing your Nginx server with multiple locations and subdomains is an effective strategy for managing complex web projects. By understanding the intricacies of location blocks and employing best practices, you can streamline your server configuration, improve resource utilization, and enhance overall website performance. Dive deeper into Nginx documentation and explore advanced features like load balancing and caching to further optimize your setup. This thoughtful approach empowers you to create a robust and scalable web infrastructure that adapts to evolving project needs. Ready to take your Nginx skills to the next level? Explore this helpful resource: Learn more about Nginx configuration. You can also find valuable information on server management from reputable sources like the official Nginx documentation, DigitalOcean’s Nginx tutorials, and Linode’s guides on Nginx configuration.

FAQ

Q: How do I prioritize location blocks in Nginx?

A: Nginx processes location blocks from most specific to least specific. Define more specific locations before more general ones.

Question & Answer :
I’m looking to serve the root url of a subdomain and directory of a subdomain to two different folders on my server. Here is the simple set-up that I have and is not working…

server { index index.html index.htm; server_name test.example.com; location / { root /web/test.example.com/www; } location /static { root /web/test.example.com/static; } } 

In this example going to test.example.com/ would bring the index file in /web/test.example.com/www

and going to test.example.com/static would bring the index file in /web/test.example.com/static

You need to use the alias directive for location /static:

server { index index.html; server_name test.example.com; root /web/test.example.com/www; location /static/ { alias /web/test.example.com/static/; } } 

The nginx wiki explains the difference between root and alias better than I can:

Note that it may look similar to the root directive at first sight, but the document root doesn’t change, just the file system path used for the request. The location part of the request is dropped in the request Nginx issues.

Note that root and alias handle trailing slashes differently.