#NGINX is similar to other services in that it has text-based configuration files written in a specific format.

By default, the file is named nginx.conf and placed in the /etc/nginx directory (for open source NGINX products, the location depends on the package used to install NGINX and the operating system system, it is usually located at /usr/local/nginx/conf/etc/nginx or /usr/local/etc/nginx.) (Recommended learning: nginx use)

A configuration file consists of directives and their parameters. Simple (single-line) instructions each end with a semicolon. Other directives act as "containers" that group related directives together, enclosed in curly braces ({}). Here are some examples of simple instructions.

user             nobody;
error_log        logs/error.log notice;
worker_processes 1;

To make the configuration easier to maintain, it is recommended that you split it into a set of feature-specific files stored in the /etc/nginx/conf.d directory and use include in the main nginx.conf file The instruction refers to the contents of the specified file. As shown below -

include conf.d/http;
include conf.d/stream;
include conf.d/exchange-enhanced;

Several top-level directives (called contexts) group together directives suitable for different traffic types:

events – general connection handling http – HTTP protocol traffic mail – Mail protocol traffic stream – TCP protocol traffic

Instructions specified outside these contexts are in the main context. Within each traffic processing context, you can include one or more server contexts to define the virtual servers that control request processing. The directives you can include in your server environment vary based on the type of traffic.

For HTTP traffic (http context), each server directive controls the processing of resource requests on a specific domain or IP address. One or more location contexts within the server context define how a specific set of URIs is processed.

For mail and TCP traffic (mail and stream contexts), server directives each control the handling of traffic arriving on a specific TCP port or UNIX socket.

The following configuration illustrates the usage of context.

user nobody; # a directive in the 'main' context

events {
    # configuration of connection processing
}

http {

    # Configuration specific to HTTP and affecting all virtual servers

    server {
        # configuration of HTTP virtual server 1

        location /one {
            # configuration for processing URIs with '/one'
        }

        location /two {
            # configuration for processing URIs with '/two'
        }
    }

    server {
        # configuration of HTTP virtual server 2
    }
}

stream {
    # Configuration specific to TCP and affecting all virtual servers

    server {
        # configuration of TCP virtual server 1 
    }
}

For most directives, a context defined within another context (a child context) will inherit the value of the directive contained in the parent. To override values ??inherited from the parent process, include this directive in the child context.

For changes to the configuration file to take effect, NGINX must reload the file. The nginx process can be restarted or the reload signal sent to upgrade the configuration without interrupting the processing of the current request.

The above is the detailed content of Detailed explanation of Nginx configuration file. For more information, please follow other related articles on the PHP Chinese website!