0Pricing
API Gateway & Reverse Proxy (Nginx + Spring Cloud Gateway) · Lesson

Basic Nginx Configuration

Understand the main Nginx configuration file structure and essential directives for simple web serving.

Basic Nginx Configuration is a free API Gateway & Reverse Proxy (Nginx + Spring Cloud Gateway) lesson on CoddyKit — lesson 2 of 4. You can read the complete lesson below for free — then practise it hands-on in the browser with a built-in code editor and a 24/7 AI tutor. It is part of the API Gateway & Reverse Proxy (Nginx + Spring Cloud Gateway) learning path, one of 4 lessons in the course, and your progress syncs across the web and the CoddyKit app.

Nginx Config: The Blueprint

Nginx uses a simple, yet powerful, configuration file to tell it what to do. Think of this file as the blueprint for your web server.

It defines how Nginx handles requests, serves content, and interacts with other services. Mastering this file is key to using Nginx effectively.

Nginx Config: Main Blocks

Nginx configuration is organized into a hierarchical structure using logical blocks. Each block groups related directives.

  • main: Global settings for the entire Nginx process.
  • events: Settings for how Nginx handles connections.
  • http: The core for all HTTP web server functionalities.

Directives inside these blocks control Nginx's specific behaviors.

user  nginx;
worker_processes  auto;

events {
    # Event context directives
}

http {
    # HTTP context directives
    # ... server blocks go here
}

Global Settings: The `main` Context

The main context contains global directives that affect the entire Nginx process. These are foundational settings for Nginx's operation.

  • user: Defines the user and group that Nginx worker processes run as (e.g., nginx or www-data).
  • worker_processes: Sets the number of worker processes. auto is often a good default, matching your CPU cores.
user  nginx;
worker_processes  auto;
error_log  /var/log/nginx/error.log warn;
pid        /var/run/nginx.pid;

Connection Handling: The `events` Context

The events context configures how Nginx handles network connections. It's about optimizing performance for concurrent clients.

  • worker_connections: The maximum number of simultaneous connections a single worker process can open.

A higher number here allows Nginx to handle more concurrent users efficiently. The use directive (e.g., epoll for Linux) specifies the connection processing method.

events {
    worker_connections  1024;
    use epoll; # Linux-specific, for high performance
}

Web Serving: The `http` Context

The http context is where most of your web server configuration resides. It defines how Nginx processes HTTP requests and responses.

Inside this block, you'll configure things like MIME types, logging, and, most importantly, define individual web servers using server blocks.

http {
    include       mime.types;
    default_type  application/octet-stream;

    sendfile        on;
    keepalive_timeout  65;

    # ... server blocks will be here ...
}

Defining Websites: `server` Blocks

Inside the http block, you define one or more server blocks. Each server block acts like a "virtual host," allowing Nginx to host multiple websites or applications on the same physical server.

It specifies what port Nginx should listen on and for which domain names it should respond.

http {
    server {
        # This is a server block for one website
    }

    server {
        # Another server block for a different site
    }
}

Server Basics: `listen` & `server_name`

Two crucial directives within a server block are listen and server_name. They tell Nginx how to identify and handle requests for a specific website.

  • listen: Specifies the IP address and port number Nginx should listen on (e.g., 80 for HTTP).
  • server_name: Defines the domain names (hostnames) this server block should respond to (e.g., example.com www.example.com).
server {
    listen       80;
    server_name  example.com www.example.com;

    # ... location blocks will be here ...
}

URL Matching: `location` Blocks

Within a server block, location blocks are used to define how Nginx should handle requests for specific URLs or URL patterns.

For instance, you might want to serve static files from one directory for requests to /images/ and handle all other requests differently.

server {
    listen 80;
    server_name mywebsite.com;

    location / {
        # Handle requests to the root path
    }

    location /api/ {
        # Handle requests starting with /api/
    }
}

Serving Files: `root` & `index`

For serving static content like HTML, CSS, and images, root and index are essential directives within a location block.

  • root: Specifies the base directory where Nginx should look for files for requests handled by this location.
  • index: Defines the default file Nginx should serve when a directory is requested (e.g., index.html).

This is how Nginx finds and delivers your website's files.

location / {
    root   /usr/share/nginx/html;
    index  index.html index.htm;
}

Full Example: Static Web Server

Let's put it all together to create a simple Nginx configuration that serves static HTML files from a specific directory.

This configuration listens on port 80 for requests to mywebsite.com and serves files from the /var/www/html directory.

http {
    include       mime.types;
    default_type  application/octet-stream;

    server {
        listen       80;
        server_name  mywebsite.com;

        location / {
            root   /var/www/html;
            index  index.html index.htm;
        }
    }
}

Quick Check: Nginx Directives

Which of the following Nginx directives are typically found within a server block, or within a location block nested inside a server block?

Recap: Nginx Config Basics

Great job! You've learned the fundamental structure of Nginx configuration, including the main, events, http, server, and location blocks.

You can now configure Nginx to listen on specific ports, respond to domain names, and serve static files effectively.

Next, we'll dive into more advanced Nginx features, including how to configure it as a reverse proxy!

Frequently asked questions

Is the “Basic Nginx Configuration” lesson free?

Yes — the full text of “Basic Nginx Configuration” is free to read here on the web, and the API Gateway & Reverse Proxy (Nginx + Spring Cloud Gateway) course includes 4 lessons in total. To practise it interactively (a built-in code editor and a 24/7 AI tutor) and unlock the rest of the API Gateway & Reverse Proxy (Nginx + Spring Cloud Gateway) course, upgrade to CoddyKit PRO.

What will I learn in “Basic Nginx Configuration”?

Understand the main Nginx configuration file structure and essential directives for simple web serving. You practise API Gateway & Reverse Proxy (Nginx + Spring Cloud Gateway) with hands-on code you run directly in the browser, and a 24/7 AI tutor answers your questions as you work through the lesson.

Do I need any experience to start API Gateway & Reverse Proxy (Nginx + Spring Cloud Gateway)?

No prior experience is required. API Gateway & Reverse Proxy (Nginx + Spring Cloud Gateway) on CoddyKit is structured for beginners through advanced learners; this is — lesson 2 of 4, so you can start here or from the beginning and move at your own pace.

How long does the “Basic Nginx Configuration” lesson take?

Most CoddyKit lessons take about 5–10 minutes. Each one is bite-sized and interactive, so you make steady progress and pick up exactly where you left off across the web and the app.

Can I write and run code in this API Gateway & Reverse Proxy (Nginx + Spring Cloud Gateway) lesson?

Yes. Every API Gateway & Reverse Proxy (Nginx + Spring Cloud Gateway) lesson includes a built-in code editor, so you write and run real code right in your browser and get instant AI feedback — no local setup required.

All lessons in this course

  1. Nginx Installation & Setup
  2. Basic Nginx Configuration
  3. Serving Static Content with Nginx
  4. Nginx Location Blocks & Request Matching
← Back to API Gateway & Reverse Proxy (Nginx + Spring Cloud Gateway)