nginx read-write separation
1. Experimental topology
Requirements analysis, front-end done by nginx Load balancing reverse proxy, two httpd servers behind. The entire architecture is to provide bbs (forum) services. There is a need to achieve separation of reading and writing, which is the function of uploading attachments. The attachments we upload can only be uploaded to web1, and then rsync inotify is used to synchronize attachments on web1. Everyone knows rsync inotify. It can only be master-to-slave synchronization, not bidirectional synchronization. Therefore, web1 can perform write operations, while web2 can only perform read operations, which brings about the need for separation of reading and writing. Let's talk about how to achieve separation of reading and writing.
2.webdav function description
webdav (web-based distributed authoring and versioning) is a communication protocol based on the http 1.1 protocol. It extends http 1.1 and adds some new methods in addition to several http standard methods such as get, post, and head, so that applications can directly read and write to the web server, and supports writing file locking and unlocking. ), and can also support file version control. In this way, we can configure the read-write separation function. Let’s configure it in detail.
3. Modify the configuration file
[root@nginx nginx]# vim /etc/nginx/nginx.conf
server {
listen 80;
server_name localhost;
#charset koi8-r;
#access_log logs/host.access.log main;
location / {
proxy_pass http://192.168.18.202;
if ($request_method = "put"){
proxy_pass http://192.168.18.201;
}
}
}4. Reload the configuration file
[root@nginx ~]# service nginx reload nginx: the configuration file /etc/nginx/nginx.conf syntax is ok nginx: configuration file /etc/nginx/nginx.conf test is successful 重新载入 nginx： [确定]
5. Configure the webdav function of httpd
[root@web1 ~]# vim /etc/httpd/conf/httpd.conf
Note, just enable it under
6. Restart httpd
[root@web1 ~]# service httpd restart 停止 httpd： [确定] 正在启动 httpd： [确定]
7. Test it
[root@nginx ~]# curl http://192.168.18.201 <h1 id="web-test-com">web1.test.com</h1> [root@nginx ~]# curl http://192.168.18.202 <h1 id="web-test-com">web2.test.com</h1>
Note, there is no problem accessing web1 and web2.
[root@nginx ~]# curl -t /etc/issue http://192.168.18.202 <!doctype html public "-//ietf//dtd html 2.0//en"> <html><head> <title>405 method not allowed</title> </head><body> <h1 id="method-nbsp-not-nbsp-allowed">method not allowed</h1> the requested method put is not allowed for the url /issue. <hr> <address>apache/2.2.15 (centos) server at 192.168.18.202 port 80</address> </body></html>
Note, when we upload files to web2, because web2 only has human-readable functions, it does not have the webdav function to open an account, so the display is 405 method not allowed.
[root@nginx ~]# curl -t /etc/issue http://192.168.18.201 <!doctype html public "-//ietf//dtd html 2.0//en"> <html><head> <title>403 forbidden</title> </head><body> <h1 id="forbidden">forbidden</h1> you don't have permission to access /issue on this server. <hr> <address>apache/2.2.15 (centos) server at 192.168.18.201 port 80</address> </body></html>
Note, we have enabled the webdav function in web1, but our directory is the root directory and apache users are not allowed to upload, so 403 forbidden is displayed. Next we authorize apache to allow uploading.
[root@web1 ~]# setfacl -m u:apache:rwx /var/www/html/
Let’s test it again,
[root@nginx ~]# curl -t /etc/issue http://192.168.18.201 <!doctype html public "-//ietf//dtd html 2.0//en"> <html><head> <title>201 created</title> </head><body> <h1 id="created">created</h1> resource /issue has been created. <hr /> <address>apache/2.2.15 (centos) server at 192.168.18.201 port 80</address> </body></html>
Note, you can see that we successfully uploaded the file, indicating that the nginx read-write separation function configuration is complete. Finally, let's take a look at the uploaded file.
[root@web1 ~]# cd /var/www/html/ [root@web1 html]# ll
Total dosage 12
drwxr-xr-x 2 root root 4096 9月 4 13:16 forum -rw-r--r-- 1 root root 23 9月 3 23:37 index.html -rw-r--r-- 1 apache apache 47 9月 4 14:06 issue
The above is the detailed content of How to configure nginx read-write separation. For more information, please follow other related articles on the PHP Chinese website!
Using NGINX Unit: Deploying and Managing ApplicationsApr 22, 2025 am 12:06 AMNGINXUnit 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 vs. Apache: A Comparative Analysis of Web ServersApr 21, 2025 am 12:08 AMNGINX 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.
NGINX Unit's Advantages: Flexibility and PerformanceApr 20, 2025 am 12:07 AMNGINXUnit 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 vs. Apache: Performance, Scalability, and EfficiencyApr 19, 2025 am 12:05 AMNGINX 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.
The Ultimate Showdown: NGINX vs. ApacheApr 18, 2025 am 12:02 AMNGINX 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 in Action: Examples and Real-World ApplicationsApr 17, 2025 am 12:18 AMNGINX 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.
NGINX Unit: Supporting Different Programming LanguagesApr 16, 2025 am 12:15 AMNGINXUnit 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.
Choosing Between NGINX and Apache: The Right Fit for Your NeedsApr 15, 2025 am 12:04 AMNGINX 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
