Installation required environment
nginx is developed in C language. It is recommended to run on Linux. Of course, you can also install the windows version. This article uses centos 7 as the installation environment.
1. gcc installation
To install nginx, you need to compile the source code downloaded from the official website first. The compilation depends on the gcc environment. If there is no gcc environment, you need to install it. :
yum install gcc-c++
2. pcre pcre-devel installation
pcre (perl compatible regular expressions) is a perl library, including perl compatible regular expressions library . The http module of nginx uses pcre to parse regular expressions, so the pcre library needs to be installed on Linux. pcre-devel is a secondary development library developed using pcre. nginx also requires this library. Command:
yum install -y pcre pcre-devel
3. zlib installation
The zlib library provides many compression and decompression methods. nginx uses zlib to gzip the contents of the http package. , so the zlib library needs to be installed on centos.
yum install -y zlib zlib-devel
4. openssl installation
openssl is a powerful secure socket layer cryptographic library, including major cryptographic algorithms, commonly used keys and The certificate encapsulates management functions and SSL protocols, and provides a rich set of applications for testing or other purposes.
nginx not only supports http protocol, but also supports https (that is, transmitting http over ssl protocol), so you need to install the openssl library on centos.
yum install -y openssl openssl-devel
Official website download
1. Directly download the .tar.gz installation package, address:
2. Use the wget command to download ( recommend).
wget -c https://nginx.org/download/nginx-1.10.1.tar.gz
I downloaded version 1.10.1, which is the current stable version.
Decompression
is still a direct command:
tar -zxvf nginx-1.10.1.tar.gz cd nginx-1.10.1
Configuration
In fact, it is in nginx-1.10. In version 1, you don’t need to configure related things, the default is fine. Of course, it is also possible if you want to configure the directory yourself.
1. Use the default configuration
./configure
2. Customize the configuration (not recommended)
./configure \ --prefix=/usr/local/nginx \ --conf-path=/usr/local/nginx/conf/nginx.conf \ --pid-path=/usr/local/nginx/conf/nginx.pid \ --lock-path=/var/lock/nginx.lock \ --error-log-path=/var/log/nginx/error.log \ --http-log-path=/var/log/nginx/access.log \ --with-http_gzip_static_module \ --http-client-body-temp-path=/var/temp/nginx/client \ --http-proxy-temp-path=/var/temp/nginx/proxy \ --http-fastcgi-temp-path=/var/temp/nginx/fastcgi \ --http-uwsgi-temp-path=/var/temp/nginx/uwsgi \ --http-scgi-temp-path=/var/temp/nginx/scgi
Note: Specify the temporary file directory For /var/temp/nginx, you need to create the temp and nginx directories under /var
Compile and install
make make install
Find the installation path:
whereis nginx
Start and stop nginx
cd /usr/local/nginx/sbin/
./nginx
./nginx -s stop
./nginx -s quit
./nginx -s reload
./nginx -s quit: The stop step in this method is to wait until the nginx process completes the task.
./nginx -s stop: This method is equivalent to first finding out the nginx process ID and then using the kill command to forcefully kill the process.
Query the nginx process:
ps aux|grep nginx
Restart nginx
1. Stop and then start (recommended):
Restarting nginx is equivalent to stopping and then starting, that is, executing the stop command first and then the start command. As follows:
./nginx -s quit ./nginx
2. Reload the configuration file:
When the ngin x configuration file nginx.conf is modified, you need to restart nginx to make the configuration take effect, use -s reload There is no need to stop ngin
./nginx -s reloadAdd a line /usr/local/nginx/sbin/nginx
Set execution permissions:
vi /etc/rc.local
The above is the detailed content of Analysis of Nginx server installation examples under CentOS7. For more information, please follow other related articles on the PHP Chinese website!

NGINXUnit can be used to deploy and manage applications in multiple languages. 1) Install NGINXUnit. 2) Configure it to run different types of applications such as Python and PHP. 3) Use its dynamic configuration function for application management. Through these steps, you can efficiently deploy and manage applications and improve project efficiency.

NGINX is more suitable for handling high concurrent connections, while Apache is more suitable for scenarios where complex configurations and module extensions are required. 1.NGINX is known for its high performance and low resource consumption, and is suitable for high concurrency. 2.Apache is known for its stability and rich module extensions, which are suitable for complex configuration needs.

NGINXUnit improves application flexibility and performance with its dynamic configuration and high-performance architecture. 1. Dynamic configuration allows the application configuration to be adjusted without restarting the server. 2. High performance is reflected in event-driven and non-blocking architectures and multi-process models, and can efficiently handle concurrent connections and utilize multi-core CPUs.

NGINX and Apache are both powerful web servers, each with unique advantages and disadvantages in terms of performance, scalability and efficiency. 1) NGINX performs well when handling static content and reverse proxying, suitable for high concurrency scenarios. 2) Apache performs better when processing dynamic content and is suitable for projects that require rich module support. The selection of a server should be decided based on project requirements and scenarios.

NGINX is suitable for handling high concurrent requests, while Apache is suitable for scenarios where complex configurations and functional extensions are required. 1.NGINX adopts an event-driven, non-blocking architecture, and is suitable for high concurrency environments. 2. Apache adopts process or thread model to provide a rich module ecosystem that is suitable for complex configuration needs.

NGINX can be used to improve website performance, security, and scalability. 1) As a reverse proxy and load balancer, NGINX can optimize back-end services and share traffic. 2) Through event-driven and asynchronous architecture, NGINX efficiently handles high concurrent connections. 3) Configuration files allow flexible definition of rules, such as static file service and load balancing. 4) Optimization suggestions include enabling Gzip compression, using cache and tuning the worker process.

NGINXUnit supports multiple programming languages and is implemented through modular design. 1. Loading language module: Load the corresponding module according to the configuration file. 2. Application startup: Execute application code when the calling language runs. 3. Request processing: forward the request to the application instance. 4. Response return: Return the processed response to the client.

NGINX and Apache have their own advantages and disadvantages and are suitable for different scenarios. 1.NGINX is suitable for high concurrency and low resource consumption scenarios. 2. Apache is suitable for scenarios where complex configurations and rich modules are required. By comparing their core features, performance differences, and best practices, you can help you choose the server software that best suits your needs.


Hot AI Tools

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Undress AI Tool
Undress images for free

Clothoff.io
AI clothes remover

Video Face Swap
Swap faces in any video effortlessly with our completely free AI face swap tool!

Hot Article

Hot Tools

Dreamweaver CS6
Visual web development tools

SAP NetWeaver Server Adapter for Eclipse
Integrate Eclipse with SAP NetWeaver application server.

MantisBT
Mantis is an easy-to-deploy web-based defect tracking tool designed to aid in product defect tracking. It requires PHP, MySQL and a web server. Check out our demo and hosting services.

Zend Studio 13.0.1
Powerful PHP integrated development environment

PhpStorm Mac version
The latest (2018.2.1) professional PHP integrated development tool