My vps has three services, which are:
The blog service built by wordpress, running on port 8000, accessed via http ://fangyuanxiaozhan.com:8000
git service built by gogs, running on port 10080, access method http://fangyuanxiaozhan.com:10080
The network disk service built by nextcloud runs on port 8080. The access method is http://fangyuanxiaozhan.com:10080
##My needs:
- 1. When accessing the blog service, directly enter http://fangyuanxiaozhan.com
- When accessing the git service, Directly enter http://git.fangyuanxiaozhan.com
- to access the network disk service, directly enter http://cloud.fangyuanxiaozhan.com
/etc/nginx/nginx .conf , interestingly,
/etc/nginx/nginx.conf introduces the configuration folder
/etc/nginx/conf.d , that is, we can put # Comment out some default configurations in ##/etc/nginx/nginx.conf
and configure multiple independent configuration files directly in the folder /etc/nginx/conf.d
.
Configuration <pre class='brush:php;toolbar:false;'># for more information on configuration, see:
# * official english documentation: http://nginx.org/en/docs/
# * official russian documentation: http://nginx.org/ru/docs/
user nginx;
worker_processes auto;
error_log /var/log/nginx/error.log;
pid /run/nginx.pid;
# load dynamic modules. see /usr/share/nginx/readme.dynamic.
include /usr/share/nginx/modules/*.conf;
events {
worker_connections 1024;
}
http {
log_format main &#39;$remote_addr - $remote_user [$time_local] "$request" &#39;
&#39;$status $body_bytes_sent "$http_referer" &#39;
&#39;"$http_user_agent" "$http_x_forwarded_for"&#39;;
access_log /var/log/nginx/access.log main;
sendfile on;
tcp_nopush on;
tcp_nodelay on;
keepalive_timeout 65;
types_hash_max_size 2048;
include /etc/nginx/mime.types;
default_type application/octet-stream;
include /etc/nginx/conf.d/*.conf;
}</pre>
Pay attention to the last line of the above configuration file,
ensures that under /etc/nginx/conf.d/
, all configuration files ending with .conf will be included in the main configuration file nginx .conf
is introduced and takes effectYou need to create three new files under
blog.conf (realizes port 8000 mapping to port 80, without using the second-level domain name)
server { listen 80; server_name fangyuanxiaozhan.com; location / { proxy_set_header x-real-ip $remote_addr; proxy_set_header host $http_host; proxy_pass http://0.0.0.0:8000; } }
blog.conf realizes mapping fangyuanxiaozhan.com:8000 to fangyuanxiaozhan.com
git.conf (Realizing port 10080 to port 80, using the second-level domain name
git)<pre class='brush:php;toolbar:false;'>server {
listen 80;
server_name git.fangyuanxiaozhan.com;
location / {
proxy_set_header x-real-ip $remote_addr;
proxy_set_header host $http_host;
proxy_pass http://0.0.0.0:10080;
}
}</pre>
git.conf implements mapping of fangyuanxiaozhan.com:10080 to git.fangyuanxiaozhan.com
nc.conf (realizes port 10080 mapping to port 80, using the second-level domain name
cloud )<pre class='brush:php;toolbar:false;'>server {
listen 80;
server_name cloud.fangyuanxiaozhan.com;
location / {
proxy_set_header x-real-ip $remote_addr;
proxy_set_header host $http_host;
proxy_pass http://0.0.0.0:8080;
}
}</pre>
git.conf realizes mapping fangyuanxiaozhan.com:8080 to cloud.fangyuanxiaozhan.com
Close nginx
sudo $(which nginx) -s stop
Open nginx
sudo $(which nginx)
Effect display
The above is the detailed content of How to configure second-level domain name in nginx. 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

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.

mPDF
mPDF is a PHP library that can generate PDF files from UTF-8 encoded HTML. The original author, Ian Back, wrote mPDF to output PDF files "on the fly" from his website and handle different languages. It is slower than original scripts like HTML2FPDF and produces larger files when using Unicode fonts, but supports CSS styles etc. and has a lot of enhancements. Supports almost all languages, including RTL (Arabic and Hebrew) and CJK (Chinese, Japanese and Korean). Supports nested block-level elements (such as P, DIV),

Dreamweaver CS6
Visual web development tools

DVWA
Damn Vulnerable Web App (DVWA) is a PHP/MySQL web application that is very vulnerable. Its main goals are to be an aid for security professionals to test their skills and tools in a legal environment, to help web developers better understand the process of securing web applications, and to help teachers/students teach/learn in a classroom environment Web application security. The goal of DVWA is to practice some of the most common web vulnerabilities through a simple and straightforward interface, with varying degrees of difficulty. Please note that this software

ZendStudio 13.5.1 Mac
Powerful PHP integrated development environment