このガイドでは、nginx の基本的な概要を説明し、nginx を使用して実行できるいくつかの簡単なタスクについて説明します。 nginx は読者のマシンにすでにインストールされているものとします。そうでない場合は、「インストール」を参照してください。 nginx ページ。このガイドでは、nginx の起動と停止、構成のリロード方法、構成ファイルの構造の説明、静的コンテンツを提供するための nginx のセットアップ方法、プロキシ サーバーとして nginx を構成する方法、および FastCGI アプリケーションに接続します。
nginx には 1 つのマスター プロセスと複数のワーカー プロセスがあります。マスター プロセスの主な目的は、構成を読み取って評価し、ワーカー プロセスを維持することです。ワーカー プロセスはリクエストの実際の処理を行います。 nginx はイベントベースのモデルと OS に依存するモデルを採用しています ワーカー プロセス間でリクエストを効率的に分散するメカニズム。ワーカー プロセスの数は構成ファイルで定義され、特定の構成に対して固定されるか、使用可能な CPU コアの数に自動的に調整されます (worker_processes を参照)。
nginx とそのモジュールの動作方法は構成ファイルで決定されます。デフォルトでは、構成ファイルの名前は nginx.conf で、ディレクトリ /usr/local/nginx/conf、/etc/nginx に配置されます。 、または /usr/local/etc/nginx。nginx.conf and placed in the directory /usr/local/nginx/conf, /etc/nginx, or /usr/local/etc/nginx.
To start nginx, run the executable file. Once nginx is started, it can be controlled by invoking the executable with the -s parameter. Use the following syntax:
nginx -s <em>signal</em>ログイン後にコピー
Where signal may be one of the following:
stop — fast shutdownquit — graceful shutdownreload — reloading the configuration filereopen nginx を起動するには、実行可能ファイルを実行します。 nginx が起動したら、-s パラメータを指定して実行可能ファイルを呼び出すことで制御できます。次の構文を使用します:
nginx -s quitログイン後にコピー
ここで、シグナルは次のいずれかになります:
stop - 高速シャットダウンquit- 正常なシャットダウン
reload - 設定ファイルの再読み込み
reopen - ログ ファイルを再度開きますkillたとえば、ワーカープロセスが現在のリクエストの処理を完了するのを待って nginx プロセスを停止するには、次のコマンドを実行できます:nginx.pid in the directory /usr/local/nginx/logs or /var/run. For example, if the master process ID is 1628, to send the QUIT signal resulting in nginx’s graceful shutdown, execute:
nginx -s reloadログイン後にコピーログイン後にコピー
For getting the list of all running nginx processes, the ps
kill -s QUIT 1628
ps -ax | grep nginx
;). A block directive has the same structure as a simple directive, but instead of the semicolon it ends with a set of additional instructions surrounded by braces ({ and}
/usr/local/nginx/logs ディレクトリまたは /var/run ディレクトリ内の nginx.pid。たとえば、マスター プロセス ID が 1628 の場合、nginx の正常なシャットダウンをもたらす QUIT シグナルを送信するには、次のコマンドを実行します。🎜🎜http {
server {
}
}
ps ユーティリティを使用します。たとえば、次の方法で使用できます:🎜🎜location / {
root /data/www;
}
Directives placed in the configuration file outside of any contexts are considered to be in the main context. Theevents and http directives reside in the main context, server in http,
and location in server.
The rest of a line after the # sign is considered a comment.
An important web server task is serving out files (such as images or static HTML pages). You will implement an example where, depending on the request, files will be served from different local directories: /data/www(which may contain HTML files)
and /data/images (containing images). This will require editing of the configuration file and setting up of a server block inside the http block
with two location blocks.
First, create the /data/www directory and put an index.html file with any text content into it and create the/data/images directory and place some images in it.
Next, open the configuration file. The default configuration file already includes several examples of the serverblock, mostly commented out. For now comment out all such blocks and start a new server block:
http { server { } }ログイン後にコピーログイン後にコピー
Generally, the configuration file may include several server blocks distinguished by ports on which they listento
and by server names. Once nginx decides which server processes a request, it tests the URI specified in the request’s header against the parameters of the location directives
defined inside the server block.
Add the following location block to the server block:
location / { root /data/www; }ログイン後にコピーログイン後にコピー
This location block specifies the “/” prefix compared with the URI from the request. For matching requests, the URI will be added to the path specified in the root directive,
that is, to /data/www, to form the path to the requested file on the local file system. If there are several matching location blocks nginx selects the one with the longest prefix. The location block above provides the
shortest prefix, of length one, and so only if all otherlocation blocks fail to provide a match, this block will be used.
Next, add the second location block:
location /images/ { root /data; }ログイン後にコピー
It will be a match for requests starting with /images/ (location / also matches such requests, but has shorter prefix).
The resulting configuration of the server block should look like this:
server { location / { root /data/www; } location /images/ { root /data; } }ログイン後にコピー
This is already a working configuration of a server that listens on the standard port 80 and is accessible on the local machine at http://localhost/. In response to requests with URIs starting with /images/, the server will send files
from the /data/images directory. For example, in response to the http://localhost/images/example.pngrequest nginx will send the /data/images/example.png file. If such file does not exist, nginx will send a response indicating
the 404 error. Requests with URIs not starting with /images/ will be mapped onto the /data/wwwdirectory. For example, in response to the http://localhost/some/example.html request nginx will send the/data/www/some/example.html file.
To apply the new configuration, start nginx if it is not yet started or send the reload signal to the nginx’s master process, by executing:
nginx -s reloadログイン後にコピーログイン後にコピー
In case something does not work as expected, you may try to find out the reason inaccess.loganderror.logfiles in the directory/usr/local/nginx/logsor/var/log/nginx.
One of the frequent uses of nginx is setting it up as a proxy server, which means a server that receives requests, passes them to the proxied servers, retrieves responses from them, and sends them to the clients.
We will configure a basic proxy server, which serves requests of images with files from the local directory and sends all other requests to a proxied server. In this example, both servers will be defined on a single nginx instance.
First, define the proxied server by adding one more server block to the nginx’s configuration file with the following contents:
server { listen 8080; root /data/up1; location / { } }ログイン後にコピー
This will be a simple server that listens on the port 8080 (previously, the listen directive has not been specified since the standard port 80 was used) and maps all requests to the /data/up1 directory on the local file system. Create
this directory and put the index.html file into it. Note that the root directive is placed in theserver context. Such root directive is used when the location block selected for serving a request
does not include own root directive.
Next, use the server configuration from the previous section and modify it to make it a proxy server configuration. In the first location block, put the proxy_pass directive
with the protocol, name and port of the proxied server specified in the parameter (in our case, it is http://localhost:8080):
server { location / { proxy_pass http://localhost:8080; } location /images/ { root /data; } }ログイン後にコピー
We will modify the second location block, which currently maps requests with the /images/ prefix to the files under the /data/images directory, to make it match the requests of images with typical file extensions. The
modified location block looks like this:
location ~ \.(gif|jpg|png)$ { root /data/images; }ログイン後にコピー
The parameter is a regular expression matching all URIs ending with .gif, .jpg, or .png. A regular expression should be preceded with ~. The corresponding requests will be mapped to the /data/images directory.
When nginx selects a location block to serve a request it first checks location directives that specify prefixes, remembering location with
the longest prefix, and then checks regular expressions. If there is a match with a regular expression, nginx picks this location or, otherwise, it picks the one remembered earlier.
The resulting configuration of a proxy server will look like this:
server { location / { proxy_pass http://localhost:8080/; } location ~ \.(gif|jpg|png)$ { root /data/images; } }ログイン後にコピー
This server will filter requests ending with .gif, .jpg, or .png and map them to the /data/images directory (by adding URI to the root directive’s parameter) and pass all other requests to the
proxied server configured above.
To apply new configuration, send the reload signal to nginx as described in the previous sections.
There are many more directives that may be used to further configure a proxy connection.
nginx can be used to route requests to FastCGI servers which run applications built with various frameworks and programming languages such as PHP.
The most basic nginx configuration to work with a FastCGI server includes using the fastcgi_pass directive instead of the proxy_pass directive,
and fastcgi_param directives to set parameters passed to a FastCGI server. Suppose the FastCGI server is accessible on localhost:9000. Taking
the proxy configuration from the previous section as a basis, replace the proxy_pass directive with the fastcgi_pass directive and change the parameter to localhost:9000. In PHP, the SCRIPT_FILENAME parameter
is used for determining the script name, and the QUERY_STRING parameter is used to pass request parameters. The resulting configuration would be:
server { location / { fastcgi_pass localhost:9000; fastcgi_param SCRIPT_FILENAME $document_root$fastcgi_script_name; fastcgi_param QUERY_STRING $query_string; } location ~ \.(gif|jpg|png)$ { root /data/images; } }ログイン後にコピー
This will set up a server that will route all requests except for requests for static images to the proxied server operating on localhost:9000 through the FastCGI protocol.
以上就介绍了Nginx: Beginner’s Guide，包括了方面的内容，希望对PHP教程有兴趣的朋友有所帮助。
![[Web フロントエンド] Node.js クイック スタート](https://img.php.cn/upload/course/000/000/067/662b5d34ba7c0227.png)
