Zinn® Cache: Use Zinn® Cache with an nginx, Varnish or Apache cache

Use Zinn® Cache with an nginx, Varnish or Apache cache

Set up Zinn® Cache on a server where nginx, Varnish, Apache or Cloudflare already caches pages, so changed pages are purged there and updates refresh the site gradually.

1. Check what is caching — In WordPress open Zinn Digital®, Cache, Status, and press Check now. If nginx, Varnish or Apache caches your pages, the screen names it, and Zinn® Cache does not add its own page cache behind it.
2. Choose your server cache — Open the Server cache tab and pick nginx, Varnish or Apache mod_cache. Choose None if nothing caches pages in front of WordPress: Zinn® Cache's own file cache then does the job.
3. Tell it how to purge — nginx: a purge request (the ngx_cache_purge module; set Send purges to http://127.0.0.1 when a CDN is in front), deleting the cache files when WordPress can read the cache folder, or a folder your host's purger reads. Varnish: its address, with PURGE or BAN allowed from the server. Apache: the CacheRoot folder, with mod_cache in a reverse-proxy virtual host.
4. Add Cloudflare if it caches your pages — Switch on Cloudflare purge and paste your zone ID and an API token limited to Cache Purge. Changed pages are then purged from Cloudflare's edge too.
5. Test one address — On the Status tab, purge one address, then load it signed out twice: the first answer is miss, the next hit. Updates and plugin activations now refresh the site a batch a minute instead of emptying every cache at once.
6. Or let us run the server — On Zinn Digital® hosting the server cache, Redis and Zinn® Cache come set up and tested together, on LiteSpeed, with nothing to configure.

With screenshots: https://zinncache.com/kb/wordpress-cache-with-nginx-varnish-or-cloudflare