Nginx configures Proxy_cache or Fastcgi_cache cache acceleration under multi site

Zhang Ge has shared many tutorials about cache acceleration on his blog, and he is constantly groping for the best website static cache acceleration scheme. Here is a brief summary:

1. Friends who use virtual hosts recommend using caching plug-ins or php code version caching scheme=> Click here to arrive directly

2. Friends who use independent hosts recommend Nginx's Fastcgi pure static cache scheme=> Click here to arrive directly

After I shared the Fastcgi cache of Nginx, many friends have succeeded. However, some friends reported that they did not know how to configure Nginx Fastcgi in a multi site environment. While all online sharing schemes are single site, I thought it would be better for multi site to directly insert the fastcgi cache configuration into the location module of php, but I found that an error will be reported, indicating that the cache space has been used.

After several rounds of testing by Zhang Ge, the Fastcgi cache configuration under multi site is finally tested. Let's share it briefly below.

1、 Deploy http module

① , single site

The previous article on a single site has been shared. Add the following configuration to the http module:

 fastcgi_cache_path /tmp/wpcache levels=1:2 keys_zone=WORDPRESS:150m inactive=31d max_size=10G; fastcgi_temp_path /tmp/wpcache/temp; fastcgi_cache_key "$scheme$request_method$host$request_uri"; fastcgi_cache_use_stale error timeout invalid_header http_500; fastcgi_ignore_headers Cache-Control Expires Set-Cookie;

② , multiple sites

When you want to enable fastcgi caching for multiple sites, the above configuration will fail and an error will be reported. After testing, it can be modified as follows:

 #Site 1 cache configuration fastcgi_cache_path /tmp/zhangge_cache levels=1:2 keys_zone=zhang.ge:384m inactive=1d max_size=5G; #Site 2 cache configuration #If you want to enable more site caches, please continue to increase them. Note that the cache path and keys_zone of each site should be customized #Ps: The parameters in the code are only examples. In actual use, please modify according to the server configuration fastcgi_cache_path /tmp/zgboke_cache levels=1:2 keys_zone=zgboke.com:384m inactive=1d max_size=5G; #Other configurations can remain unchanged fastcgi_temp_path /tmp/temp_cache; fastcgi_cache_key "$scheme$request_method$host$request_uri"; fastcgi_cache_use_stale error timeout invalid_header http_500;

2、 Deploy server module

After the http module is configured, the server module is very simple!

Just insert different fastcgi cache configurations under the php modules of different sites. In fact, this is just the difference between key_zones.

For example, I configured Zhang Ge Blog and China Blog Alliance at the same time as follows:

Zhang Ge's blog:

 server( #Other configurations are omitted location ~ [^/]\.php(/|$) { try_files $uri =404; fastcgi_pass  unix:/dev/shm/php-cgi.sock; fastcgi_index index.php; include fastcgi.conf; #Fastcgi cache configuration fastcgi_cache_bypass $skip_cache; fastcgi_no_cache $skip_cache; add_header X-Cache "$upstream_cache_status From $host"; fastcgi_cache zhang.ge; fastcgi_cache_valid 200 301 302 1d; } #Other configurations are omitted }

China Blog Alliance:

 server( #The above configuration is omitted location ~ [^/]\.php(/|$) { try_files $uri =404; fastcgi_pass  unix:/dev/shm/php-cgi.sock; fastcgi_index index.php; include fastcgi.conf; #Fastcgi cache configuration fastcgi_cache_bypass $skip_cache; fastcgi_no_cache $skip_cache; add_header X-Cache "$upstream_cache_status From $host"; fastcgi_cache zgboke.com; fastcgi_cache_valid 200 301 302 1d; } #The following configurations are omitted }

In fact, it is just a one-to-one correspondence with the cache defined in the http module, which can be distinguished! Otherwise, an error will be reported.

3、 Proxy_cache cache

We shared the fastcgi cache configuration of multi sites, and also shared the Proxy_cache cache configuration of multi sites. In case some friends don't follow suit...

In fact, I didn't actually test it, but by analogy, it should be configured as follows:

① , http module

 proxy_connect_timeout 5; proxy_read_timeout 60; proxy_send_timeout 5; proxy_buffer_size 16k; proxy_buffers 4 64k; proxy_busy_buffers_size 128k; proxy_temp_file_write_size 128k; #There are also several proxy_cache_paths configured for several sites. Note that the cache path and keys_zone need to be customized #Ps: The parameters in the code are only examples. In actual use, please modify according to the server configuration proxy_cache_path /tmp/web1_cache levels=1:2 keys_zone=web1_cache:256m inactive=31d max_size=2g; proxy_cache_path /tmp/web2_cache levels=1:2 keys_zone=web2_cache:256m inactive=31d max_size=2g; proxy_temp_path /tmp/temp_cache;

② , server module

As for the server module, it should not be as detailed as the above description! The only difference between different sites is the proxy_cache configuration! For example:

Site 1 Configuration

 #Other configurations are omitted Proxy_cache web1_cache; # Fill in the keys_zone corresponding to the site proxy_cache_valid 200 302 304 301 1d; proxy_cache_valid any 1m;

Site 2 configuration:

 #Other configurations are omitted Proxy_cache web2_cache; # Fill in the keys_zone corresponding to the site proxy_cache_valid 200 302 304 301 1d; proxy_cache_valid any 1m;

Ps: Maybe someone will ask again, where is the configuration? Alas, what are you doing here? Write honestly!

Oh, understand the above configuration, and don't worry about deploying any number of sites' fastcgi or proxy caches!