Hi @ffemtkl,
To set up multisite with FastCGI Cache, one site will be configured like this:
fastcgi_cache_path /var/lib/nginx/siteone levels=1:2 keys_zone=SITEONE:1440m;
server {
location ~ \.php$ {
fastcgi_cache SITEONE;
}
}
and the second site like this:
fastcgi_cache_path /var/lib/nginx/sitetwo levels=1:2 keys_zone=SITETWO:1440m;
server {
location ~ \.php$ {
fastcgi_cache SITETWO;
}
}
Within the plugin settings for site one, make sure the CachePath
is set to /var/lib/nginx/siteone
Likewise for site two, set the CachePath
to /var/lib/nginx/sitetwo
Hope this helps.
-
This reply was modified 5 years, 6 months ago by robertchen617. Reason: formatting code block
Thanks for pointing that out!
If you are scaling out with many new sites it is not very scalable with the above method.
I was looking for something in the network menu where you only have one /var/lib/nginx/
folder and have all site store cache there.
Any ideas?
Unfortunately, we haven’t really tested this plugin with multisite (that is, where multiple sites are using the same WordPress core).
Are you currently using FastCGI cache with your current set up? If so, are you able to separate each site’s cache files into their own folders?
Thanks,
Robert
I am using FastCGI currently but storing all the sites in subfolders based on the MD5 hash. Meaning ‘e3i445873845’ would be under /e/ and so forth. I am currently trying to figure out how I can store it more organized so it is by site.
Yeah, the MD5 hash levels 1:2 (i.e. /e/3i/e3i445873845) makes it really hard to keep sites separate.
It might be easier to just have a separate Nginx virtual host conf for each website (regardless of whether you’re using multisite or multiple site WordPress). That way, you can leverage the keys_zone
to separate each website into different folder paths.
If there’s another way of doing this, I’m not aware of it.