


How to use Nginx open source visual configuration tool NginxConfig
NginxConfig Introduction
NginxConfig
Known asThe only Nginx configuration tool you need, you can use the visual interface to generate Nginx configuration, the function is very powerful, it is available on Github There are 15K Star
!
The following is a rendering of the use of NginxConfig, you can take a look!
Installation
Next, we will introduce the installation of
NginxConfig
. It is relatively convenient to install it on Linux.
Install Node.js
Since
NginxConfig
is a front-end project based on Vue, we must first installNode.js
.
First download the installation package of Node.js
from the official website
Download address: https://nodejs.org/zh-cn/download/
After the download is successful, unzip the installation package to the /usr/local/src/
directory and use the following command;
cd /usr/local/src/ tar xf node-v16.14.2-linux-x64.tar.xz cd node-v16.14.2-linux-x64/ ./bin/node -v
Use the ./bin/node -v
command to view the currently installed version;
If you want to run it directly from the Linux command line, you also need to # The ##node and
npm commands create soft links;
ln -s /usr/local/src/node-v16.14.2-linux-x64/bin/node /usr/bin/node ln -s /usr/local/src/node-v16.14.2-linux-x64/bin/npm /usr/bin/npm node -v npm -vAfter the creation is completed, use the command to view the version. At this point, the
Node.js installation is complete.
First download the installation package ofNode.js
After the installation is complete, you can start the installation
NginxConfig.
NginxConfig,
npm command to install the dependencies and run it;
tar -zxvf nginxconfig.io-master.tar.gz npm install npm run dev
NginxConfigAfter successful operation, You can access it directly. It is quite good to see that the interface supports Chinese. Access address: http://192.168.3.105:8080
Next we will experience the visual configuration generation function ofPreparation for useFirst we need to install Nginx. For Nginx installation, please refer to the Nginx usage tutorial written before; We will implement the following functions through static proxy To access static websites in different directories, access the API interface provided by SpringBoot through a dynamic proxy;NginxConfig
to see if it is powerful enough!
# 静态代理,访问mall文档网站 docs.macrozheng.com # 静态代理,访问mall前端项目 mall.macrozheng.com # 动态代理,访问mall线上API api.macrozheng.comYou need to modify the local host file in advance.
192.168.3.105 docs.macrozheng.comDocumentation website Configuration192.168.3.105 mall.macrozheng.com
192.168.3.105 api.macrozheng.com
Let’s first configure access to the mall document website. The domain name is: docs.macrozheng.com.Select
default as the front end in
NginxConfig, then modify the service configuration, configure the site, path and running directory;
Global Configuration->Security
Content-Security-Policy Settings;
Performance configuration, enable Gzip compression, and delete the resource validity limit.
Let’s configure access to the mall front-end website. The domain name is: mall.macrozheng.com.Next we add another site and modify the service configuration. The rest is basically the same as above.
API网站配置
最后配置下mall的Swagger API文档网站的访问,域名为:api.macrozheng.com。
继续添加一个站点,修改服务配置,只需修改站点名称即可;
然后启用反向代理并设置,反向代理到线上API;
路由功能暂时不用可以关闭。
使用配置 接下来我们就可以直接下载NginxConfig
给我们生成好的配置了;
我们先来看下NginxConfig
给我们生成的配置内容,这种配置手写估计要好一会吧;
点击按钮下载配置,完成后改个名字,然后上传到Linux服务器的Nginx配置目录下,使用如下命令解压;
tar -zxvf nginxconfig.io.tar.gz
大家可以看到NginxConfig
将为我们生成如下配置文件;
接下来将我们之前的mall文档网站和mall前端网站放到Nginx的html目录下,然后重启Nginx就可以查看效果了;
docker restart nginx
先访问下我们的mall文档网站,访问地址:http://docs.macrozheng.com/
在访问下mall的前端网站,访问地址:http://mall.macrozheng.com
最后访问下mall的API文档网站,访问地址:http://api.macrozheng.com/swagger-ui.html
The above is the detailed content of How to use Nginx open source visual configuration tool NginxConfig. For more information, please follow other related articles on the PHP Chinese website!

NGINX is suitable for handling high concurrency and static content, while Apache is suitable for dynamic content and complex URL rewrites. 1.NGINX adopts an event-driven model, suitable for high concurrency. 2. Apache uses process or thread model, which is suitable for dynamic content. 3. NGINX configuration is simple, Apache configuration is complex but more flexible.

NGINX and Apache each have their own advantages, and the choice depends on the specific needs. 1.NGINX is suitable for high concurrency, with simple deployment, and configuration examples include virtual hosts and reverse proxy. 2. Apache is suitable for complex configurations and is equally simple to deploy. Configuration examples include virtual hosts and URL rewrites.

The purpose of NGINXUnit is to simplify the deployment and management of web applications. Its advantages include: 1) Supports multiple programming languages, such as Python, PHP, Go, Java and Node.js; 2) Provides dynamic configuration and automatic reloading functions; 3) manages application lifecycle through a unified API; 4) Adopt an asynchronous I/O model to support high concurrency and load balancing.

NGINX started in 2002 and was developed by IgorSysoev to solve the C10k problem. 1.NGINX is a high-performance web server, an event-driven asynchronous architecture, suitable for high concurrency. 2. Provide advanced functions such as reverse proxy, load balancing and caching to improve system performance and reliability. 3. Optimization techniques include adjusting the number of worker processes, enabling Gzip compression, using HTTP/2 and security configuration.

The main architecture difference between NGINX and Apache is that NGINX adopts event-driven, asynchronous non-blocking model, while Apache uses process or thread model. 1) NGINX efficiently handles high-concurrent connections through event loops and I/O multiplexing mechanisms, suitable for static content and reverse proxy. 2) Apache adopts a multi-process or multi-threaded model, which is highly stable but has high resource consumption, and is suitable for scenarios where rich module expansion is required.

NGINX is suitable for handling high concurrent and static content, while Apache is suitable for complex configurations and dynamic content. 1. NGINX efficiently handles concurrent connections, suitable for high-traffic scenarios, but requires additional configuration when processing dynamic content. 2. Apache provides rich modules and flexible configurations, which are suitable for complex needs, but have poor high concurrency performance.

NGINX and Apache each have their own advantages and disadvantages, and the choice should be based on specific needs. 1.NGINX is suitable for high concurrency scenarios because of its asynchronous non-blocking architecture. 2. Apache is suitable for low-concurrency scenarios that require complex configurations, because of its modular design.

NGINXUnit is an open source application server that supports multiple programming languages and provides functions such as dynamic configuration, zero downtime updates and built-in load balancing. 1. Dynamic configuration: You can modify the configuration without restarting. 2. Multilingual support: compatible with Python, Go, Java, PHP, etc. 3. Zero downtime update: Supports application updates that do not interrupt services. 4. Built-in load balancing: Requests can be distributed to multiple application instances.


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

SublimeText3 Linux new version
SublimeText3 Linux latest version

SublimeText3 Chinese version
Chinese version, very easy to use

Dreamweaver CS6
Visual web development tools

EditPlus Chinese cracked version
Small size, syntax highlighting, does not support code prompt function

WebStorm Mac version
Useful JavaScript development tools
