Dan Collis-Puro

Need for Speed?
This plugin handles the wordpress/php side of a statically cached nginx-fronted wordpress (or wordpress mu) site. It makes WordPress emit an “X-Accel-Expires: 0” header when a user is logged in or has taken actions that should cause them to get a customized page on your frontend. This – along with the nginx configuration below – will ensure logged-in users aren’t impacted by your static nginx cache.
Why would you want to statically cache wordpress with <a href="http://www.nginx.org" rel="nofollow ugc">nginx?</a>
<ul>
<li>INSANE performance. Hardware that could generate 6 pages / second can now generate many thousands.</li>
<li>Low resource usage. Even on very busy servers, nginx uses only a handful of RAM.</li>
<li>Unobtrusiveness. You plop nginx in front of wordpress and that’s pretty much it. This plugin (and nginx) is all you need to make your site digg- and slashdot- proof.</li>
<li>Stability. Nginx is rock solid.</li>
<li>Faster is better. All the web gurus agree – visitors like faster sites, even when the differences are slight.</li>
<li>Do more with less. Using a frontend proxy lets you keep your heavy wordpress apaches lightly loaded, letting you handle more concurrent connections and use less RAM.</li>
</ul>
We’ve been using a caching nginx proxy at the fairly busy <a href="http://blogs.law.harvard.edu" rel="nofollow ugc">blogs.law.harvard.edu</a> since September, 2009. The results have been dramatic: we’ve halved the amount of RAM we need, doubled our outgoing network throughput (nginx is fast!) and have had essentially no significant load spikes.
Drawbacks
There are a few.
<ul>
<li>Plugins that rely on php code running on each page view won’t work properly. This is similar to wp-supercache or any of the other static caching plugins. Stats, image rotation, etc. You should implement these features via javascript or third-party services, depending. </li>
<li>You need to install and configure an nginx frontend proxy – but see the “installation” tab. It’s really not that hard.</li>
</ul>
Notes
<ul>
<li>It is completely harmless to install and activate this plugin before you’ve got the nginx side set up.</li>
<li>YOU MUST keep this plugin activated as long as you’ve got an nginx frontend proxy active – otherwise, you’ll end up caching too much of your site, and authenticated users won’t see customized pages.</li>
<li>This plugin helps speed up access for authenticated users mainly because it makes all other traffic a negligible resource drain. I suggest installing <a href="http://php.net/manual/en/book.apc.php" rel="nofollow ugc">apc</a> (or another opcode cache) and – alternatively – a wordpress object cache. Definitely install an opcode cache – leave the object cache for later. You may find you don’t need it!</li>
</ul>
<h3>The Future</h3>
This plugin could be set up to allow you to manage caching policies entirely from a wordpress control panel. We’d do this by manipulating the timeout in the “X-Accel-Expires” header based on the type of resource that’s been requested.
It’d be nice to de-cache when pages change via some call from the backend to the nginx frontend.

WordPress Nginx proxy cache integrator

Enables your blog to work properly with an nginx frontend static proxy cache. ASTRONOMICAL performance is yours!

Merlot Digital (by TNC)

TNC Toolbox aims to enhance your WordPress experience with NGINX-on-cPanel (ea-nginx).
Built for our Managed Server clients, we’ve open-sourced it so others can enjoy it too!
With a heavy focus on the Apache + NGINX as Reverse Caching Proxy web stack, the plugin aims to help with Website Management, Performance and Security.
<blockquote>
❤️ FOSS by <a href="https://tnc.works" rel="nofollow ugc">The Network Crew Pty Ltd</a> (TNC) for <a href="https://merlot.digital" rel="nofollow ugc">Merlot Digital</a> & the world. ❤️
</blockquote>
<h3>Functionality</h3>
At the moment, TNC Toolbox:
<ul>
<li>Allows you to enable, disable and purge the NGINX User Cache</li>
<li>Purges the NGINX Cache magically on post/page publish/update!</li>
<li>Also purges the Cache when the WP Core is successfully updated</li>
<li>Lets you know if the plugin is activated but not yet configured</li>
<li>Only allows Admins to enable/disable caching & edit configs</li>
<li>Shows you the status of cP UAPI via disk usage info</li>
<li>Purge when any ACF config options are saved</li>
<li>Supports scheduled post publishing!</li>
</ul>
Eager for even more capabilities?
We plan to add further features as clients & the community request it.
Please let us know your ideas on <a href="https://github.com/The-Network-Crew/TNC-Toolbox-for-WordPress/" rel="nofollow ugc">GitHub</a> – we’d love to hear from you!
<h3>Caching Deployments</h3>
Caching ideals: 
– Don’t forget, ea-NGINX (reverse proxy caching) is meant to be 2nd-level 
– ie. Make sure your WP site also has on-site caching, like WP Super Cache 
– You can go further with caching, and should: like browser-caching assets!
3-layer Cache: 
1. NGINX Caching Proxy (ahead of Apache) 
2. WP Super Cache, WP Rocket, etc on-site 
3. htaccess/etc rules for Browser Caching
This way, you can ensure maximum efficiency!
The key is to purge when stale, so properly configuring your WP Plugin Cache is critical to ensuring that you don’t end up with cache misses due to stale data that could’ve/should’ve been purged by garbage collection, preloading, etc, rule-sets.
<h3>Updating from v1 to v2.x.x</h3>
On every website running the plugin, check that:
<ol>
<li>Website is reporting v2.x.x plugin version.</li>
<li>Plugin has been activated post-update. *</li>
<li>Config exists in the plugin settings.</li>
<li>API status checker reports OK.</li>
<li>/wp-content/tnc-toolbox-config/ folder is gone.</li>
</ol>
(* Change to main plugin file name may result in deactivation)
<h3>Verifying cP+WHM Logs</h3>
If you’d like to ensure actions are firing properly at a deeper level:
<ol>
<li>WHM > Tweak Settings > Logging > Enable cPanel API Log > On</li>
<li>WHM > Terminal > <code>tail -f /usr/local/cpanel/logs/api_log</code></li>
<li>WordPress > Update a Post/Page, or explicitly Purge</li>
<li>WHM > Terminal > You should see the action fire!</li>
<li>WHM > Terminal > Ctrl+C to close the tail</li>
</ol>
Note: To do this, you require <code>root</code> access to the Server.

TNC Toolbox: Web Performance

Designed for ea-NGINX (Cache/Proxy) on cPanel+WHM. Made to help you fly online! 🚀

WordPress Nginx proxy cache integrator vs TNC Toolbox: Web Performance