Temel Nginx Yapılandırması

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 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.

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.

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.

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.

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.

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).

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.

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.

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.

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

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!