Usually, the connection processing method is automatically selected based on the most efficient choice that the platform has available. Mainly, directives found here are used to either select the connection processing technique to use, or to modify the way these methods are implemented. Nginx uses an event-based connection processing model, so the directives defined within this context determine how worker processes should handle connections. This context will look like this in the configuration file, outside of any other bracketed contexts: # main context There can only be a single events context defined within the Nginx configuration. It is used to set global options that affect how Nginx handles connections at a general level. The “events” context is contained within the “main” context. The default error file for the entire application can be set at this level (this can be overridden in more specific contexts). You can even define things like worker CPU affinity and the “niceness” of worker processes. Some common details that are configured in the main context are the user and group to run the worker processes as, the number of workers, and the file to save the main process’s PID. While the directives in this section affect the lower contexts, many of these aren’t inherited because they cannot be overridden in lower levels. It is used to configure details that affect the entire application on a basic level. The main context represents the broadest environment for Nginx configuration. Keep in mind that if your Nginx configuration is set up in a modular fashion, some files will contain instructions that appear to exist outside of a bracketed context, but which will be included within such a context when the configuration is stitched together. It is the only context that is not contained within the typical context blocks that look like this: # The main context is here, outside any other contextsĪny directive that exist entirely outside of these blocks is said to inhabit the “main” context. The most general context is the “main” or “global” context. These are the contexts that comprise the major structure of an Nginx configuration. The first group of contexts that we will discuss are the core contexts that Nginx utilizes in order to create a hierarchical tree and separate the concerns of discrete configuration blocks. The Nginx documentation contains information about which contexts each directive is valid in, so it is a great reference if you are unsure.īelow, we’ll discuss the most common contexts that you’re likely to come across when working with Nginx. Nginx will error out on reading a configuration file with directives that are declared in the wrong context. It is worth noting that an override to any array-type directives will replace the previous value, not append to it.ĭirectives can only be used in the contexts that they were designed for. The children contexts can override these values at will. As a general rule, if a directive is valid in multiple nested scopes, a declaration in a broader context will be passed on to any child contexts as default values. Basically, these divisions provide an organizational structure along with some conditional logic to decide whether to apply the configurations within.īecause contexts can be layered within one another, Nginx provides a level of directive inheritance. In Nginx parlance, the areas that these brackets define are called “contexts” because they contain configuration details that are separated according to their area of concern. One of the first things that you should notice when looking at the main configuration file is that it appears to be organized in a tree-like structure, defined by sets of brackets (that look like ). If it does not exist there, it may also be at /usr/local/nginx/conf/nf or /usr/local/etc/nginx/nf. For many distributions, the file will be located at /etc/nginx/nf.
#Multiple contexts have a path of software#
The location of this file will vary depending on how you installed the software on your machine. This guide will cover the basic structure found in the main Nginx configuration file. Understanding Nginx Configuration Contexts
#Multiple contexts have a path of how to#
In this guide, we will focus on discussing the basic structure of an Nginx configuration file along with some guidelines on how to design your files.
While many users are aware of Nginx’s capabilities, new users are often confused by some of the conventions they find in Nginx configuration files. It is especially good at handling many concurrent connections and excels at serving static content. Nginx is a high performance web server that is responsible for handling the load of some of the largest sites on the internet.
0 kommentar(er)
