Nginx : Virtual hosting using Location directives

This setup demonstrates a virtual container-based environment in Nginx where multiple locations are configured under a single server block, rather than a load-balancing mechanism. Each location serves a different application based on its respective directory structure.

The Pitfalls of add_header in NGINX: Solving Inheritance Issues with more_set_headers - GetPageSpeed

Nginx Configuration

Server Configuration

server {
    listen 80;
    server_tokens off;
    server_name _;
    client_max_body_size 35M;
    charset utf-8;
    large_client_header_buffers 4 16k;
    root /usr/share/nginx/server1;
    index index.html index.php index.cgi;
    
    access_log /var/log/nginx/access.log;
    error_log /var/log/nginx/error.log;

    location /server2 {
        root /usr/share/nginx/;
        index index.html index.php index.cgi;
        access_log /var/log/nginx/access.log;
        error_log /var/log/nginx/error.log;
    }
    
    location /server3 {
        root /usr/share/nginx/;
        index index.html index.php index.cgi;
        access_log /var/log/nginx/access.log;
        error_log /var/log/nginx/error.log;
    }
}

Directory Structure

Each application is stored under a separate directory within /usr/share/nginx/.

Application Directories and Content

[root@server1 conf.d]# cat /usr/share/nginx/server1/index.html
Application 1

[root@server1 conf.d]# cat /usr/share/nginx/server2/index.html
Application 2

[root@server1 conf.d]# cat /usr/share/nginx/server3/index.html
Application 3

Explanation

  1. Main Root (/usr/share/nginx/server1/): This serves as the default root for the server.

  2. Location ****/server2:

    • Serves content from /usr/share/nginx/server2/

    • Allows access through http://server_ip/server2

  3. Location ****/server3:

    • Serves content from /usr/share/nginx/server3/

    • Allows access through http://server_ip/server3

Testing the Setup

Run the following commands to verify the setup:

curl http://localhost/       # Should return "Application 1"
curl http://localhost/server2  # Should return "Application 2"
curl http://localhost/server3  # Should return "Application 3"

Conclusion

This setup allows serving multiple applications on different paths without using multiple virtual hosts or load balancing. It is useful for lightweight multi-container setups or development environments.




=======================================================================
Thank you, check out more blogs for such information..!
For any queries,feel free to reach out me on shubhammore07007@gmail.com

Comments

Post a Comment

Popular posts from this blog

Terraform project with AWS to build infra within seconds! (Web Ec2 with eIP)

Image
1. Introduction: What is Terraform? Terraform is an open-source Infrastructure as Code (IaC) tool created by HashiCorp. It lets you define, provision, and manage cloud infrastructure using declarative configuration files . Instead of manually creating AWS resources in the console, you write code that describes what you want, and Terraform takes care of creating or updating it. Why use it with AWS? a) Infrastructure as Code (IaC) You can define AWS resources (EC2, VPC, S3, IAM, etc.) in .tf files. These configurations can be version-controlled in Git. b) Multi-Cloud Support Although AWS has its own tool (CloudFormation), Terraform works with AWS + Azure + GCP + on-prem at the same time. c) Reusability & Automation You can reuse Terraform modules to deploy the same AWS setup in different environments (dev, test, prod). d) State Management Terraform keeps a state file to know which resources it manages. Makes it easy to track and update changes in AWS without accidentally del...
Read more

AWS: Serverless REST API (API Gateway + Lambda + DynamoDb + WAF)

Image
This project demonstrates a secure, scalable, and cost-efficient serverless REST API built using API Gateway, Lambda, DynamoDB, and protected by WAF. The architecture ensures high availability, automatic scaling, and IP-based access control for write operations, making it production-ready  Architecture: Client → API Gateway → Lambda → DynamoDB 🟢 STEP 1: Create DynamoDB Table: > Go to AWS Console > Search → DynamoDB > Click Create table Fill: Table name: users Partition key: Name: id Type: String Keep On-demand capacity > Click Create table ✅ Done. 🟢 STEP 2: Create IAM Role for Lambda: > Go to IAM > Click Roles > Click Create role > Select: Trusted entity: AWS Service Use case: Lambda > Click Next > Attach policies: AWSLambdaBasicExecutionRole AmazonDynamoDBFullAccess (For learning project. In real production, use limited custom policy.) > Name role: lambda-dynamodb-role > Click Create role ✅ Done. 🟢 STEP 3: Create Lambda Function > Go to La...
Read more

Nginx : Setting Up Nginx with Load Balancing

Image
This guide explains how to configure Nginx as a load balancer for multiple backend applications running on different ports. The setup includes three application servers running on ports 8001, 8002, and 8003, with Nginx balancing requests among them.   Nginx Configuration Details Individual Server Blocks Each backend application is configured as an independent Nginx server block: Server 1 Configuration ( server1.conf ) [root@server1 conf.d]# cat /etc/nginx/conf.d/server1.conf | grep -v "#"   server { listen 8001; server_tokens off; server_name _; client_max_body_size 35M; charset utf-8; large_client_header_buffers 4 16k; root /usr/share/nginx/server1; index index.html index.php index.cgi; access_log /var/log/nginx/access.log; error_log /var/log/nginx/error.log; } Server 2 Configuration ( server2.conf ) [root@server1 conf.d]# cat /etc/nginx/conf.d/server2.conf | grep -v "#"     server { listen 8002; server_tokens off;...
Read more