First Nginx configuration - Step-by-Step Execution

Process Flow - First Nginx configuration

Start Nginx

↓

Read nginx.conf

↓

Parse main context

↓

Parse http context

↓

Parse server block

↓

Apply server settings

↓

Listen on port

↓

Serve requests

↓

Log requests

↓

End

Nginx starts, reads its main config file, parses contexts and server blocks, applies settings, listens on ports, and serves requests.

Execution Sample

Nginx

server {
    listen 80;
    server_name example.com;
    location / {
        root /usr/share/nginx/html;
    }
}

This config defines a server listening on port 80 for example.com, serving files from /usr/share/nginx/html.

Process Table

Step	Action	Config Part	Result
1	Start Nginx process	N/A	Nginx process begins
2	Read config file	nginx.conf	Config file loaded
3	Parse main context	main	Global settings loaded
4	Parse http context	http	HTTP settings loaded
5	Parse server block	server	Server block recognized
6	Apply listen directive	listen 80;	Nginx will listen on port 80
7	Apply server_name directive	server_name example.com;	Server responds to example.com
8	Parse location block	location /	Root location configured
9	Apply root directive	root /usr/share/nginx/html;	Files served from this directory
10	Start listening	port 80	Nginx ready to accept requests
11	Serve incoming request	GET /	Serve index.html from root
12	Log request	access log	Request logged
13	End	N/A	Nginx running and serving

💡 Nginx continues running, serving requests until stopped

Status Tracker

Variable	Start	After Step 6	After Step 7	After Step 9	Final
listen_port	none	80	80	80	80
server_name	none	none	example.com	example.com	example.com
root_path	none	none	none	/usr/share/nginx/html	/usr/share/nginx/html

Key Moments - 3 Insights

Why does Nginx need the 'listen' directive?

The 'listen' directive tells Nginx which port to wait for requests on. Without it, Nginx won't know where to accept connections. See execution_table step 6.

What happens if 'server_name' does not match the request?

Nginx will not use this server block for that request and may use a default server block instead. This is why 'server_name' defines which domain this block serves. See execution_table step 7.

How does the 'root' directive affect serving files?

The 'root' directive sets the folder where Nginx looks for files to serve for matching requests. Without it, Nginx won't find the files. See execution_table step 9.

Visual Quiz - 3 Questions

Look at the execution_table, what is the value of 'listen_port' after step 6?

A 443

B 80

C none

D 8080

💡 Hint

Check variable_tracker column 'After Step 6' for 'listen_port'

At which step does Nginx start listening on port 80?

A Step 5

B Step 6

C Step 10

D Step 12

💡 Hint

See execution_table row describing 'Start listening' action

If the 'root' directive was missing, what would change in the execution_table?

A Step 9 would be missing or have no root path

B Step 6 would change to port 443

C Server block would not be parsed

D Nginx would not start

💡 Hint

Look at step 9 where 'root' is applied

Concept Snapshot

Nginx configuration starts with a server block.
Use 'listen' to set port (e.g., 80).
Use 'server_name' to match domain.
Use 'location' and 'root' to serve files.
Nginx reads config, applies settings, then serves requests.

Full Transcript

This visual execution shows how Nginx starts and reads its configuration file. It parses the main and HTTP contexts, then finds the server block. The 'listen' directive sets the port to 80, and 'server_name' defines the domain example.com. The location block with 'root' sets the folder for files. After applying these settings, Nginx listens on port 80 and serves requests, logging each one. Variables like listen_port, server_name, and root_path update step-by-step. Key points include the importance of 'listen' for port binding, 'server_name' for domain matching, and 'root' for file serving. The quiz checks understanding of these steps and variable values.

Practice

1. What is the purpose of the server block in an Nginx configuration?

easy

A. To start the Nginx service

B. To define settings for a specific website or domain

C. To specify the operating system

D. To install Nginx modules

Solution

1. Step 1: Understand Nginx configuration structure

   Nginx uses server blocks to group settings for each website or domain it serves.

2. Step 2: Identify the role of server block

   The server block tells Nginx how to handle requests for a particular site, including ports and root folder.

3. Final Answer:

   To define settings for a specific website or domain -> Option B

4. Quick Check:

   server block = website settings [OK]

Hint: Remember: server block = one website config [OK]

Common Mistakes:

• Confusing server block with service start command
• Thinking server block installs software
• Mixing server block with OS settings

2. Which of the following is the correct syntax to listen on port 80 in an Nginx server block?

easy

A. listen: 80

B. listen = 80;

C. listen 80;

D. port 80;

Solution

1. Step 1: Recall Nginx directive syntax

   Nginx directives end with a semicolon and use space-separated key and value.

2. Step 2: Check the correct listen syntax

   The correct way to specify port 80 is listen 80; without equals or colon.

3. Final Answer:

   listen 80; -> Option C

4. Quick Check:

   listen 80; = correct syntax [OK]

Hint: Nginx directives end with semicolon, no equals sign [OK]

Common Mistakes:

• Using equals sign (=) in directives
• Using colon (:) instead of space
• Omitting semicolon at end

3. Given this Nginx configuration snippet, what is the root folder for the website?

server {
    listen 80;
    root /var/www/html;
    index index.html;
}

medium

A. /home/user

B. /etc/nginx

C. /usr/share/nginx

D. /var/www/html

Solution

1. Step 1: Locate the root directive

   The root directive sets the folder where website files are served from.

2. Step 2: Read the root path value

   Here, root /var/www/html; means the website files are in /var/www/html.

3. Final Answer:

   /var/www/html -> Option D

4. Quick Check:

   root folder = /var/www/html [OK]

Hint: Look for root directive to find website folder [OK]

Common Mistakes:

• Confusing root with index directive
• Assuming default folder without checking config
• Mixing root with Nginx installation folders

4. Identify the error in this Nginx configuration snippet:

server {
    listen 80
    root /var/www/html;
    index index.html;
}

medium

A. Missing semicolon after listen 80

B. Wrong root path

C. index directive should be index.htm

D. listen directive should be inside location block

Solution

1. Step 1: Check syntax of each directive

   Each directive must end with a semicolon in Nginx configuration.

2. Step 2: Identify missing semicolon

   The line listen 80 is missing a semicolon at the end.

3. Final Answer:

   Missing semicolon after listen 80 -> Option A

4. Quick Check:

   Every directive ends with ; [OK]

Hint: Check every line ends with semicolon [OK]

Common Mistakes:

• Forgetting semicolon after directives
• Placing listen inside location block incorrectly
• Changing root path without reason

5. You want to serve a website on port 8080 with files located in /home/user/site and the main page named home.html. Which Nginx server block is correct?

hard

A. server {
listen 8080;
root /home/user/site;
index home.html;
}

B. server {
listen 80;
root /home/user/site;
index home.html;
}

C. server {
listen 8080;
root /var/www/html;
index index.html;
}

D. server {
listen 8080;
root /home/user/site;
index index.html;
}

Solution

1. Step 1: Match the listen port

   The question requires port 8080, so listen 8080; is needed.

2. Step 2: Match root and index directives

   Root must be /home/user/site and index must be home.html as given.

3. Final Answer:

   server { listen 8080; root /home/user/site; index home.html; } -> Option A

4. Quick Check:

   Port 8080 + correct root + correct index = server { listen 8080; root /home/user/site; index home.html; } [OK]

Hint: Match all three: listen, root, index exactly [OK]

Common Mistakes:

• Using default port 80 instead of 8080
• Wrong root folder path
• Wrong index file name