SpinupWP

This plugin ensures that the SpinupWP page cache is cleared when your site’s content changes. Not using SpinupWP yet? <a href="https://spinupwp.com/pricing/" rel="nofollow ugc">Sign up here.</a>
SpinupWP is a modern server control panel that’s here to help you implement best practices for every server you spin up. Designed for WordPress.
This companion plugin should be installed on sites created using SpinupWP to allow the page cache to be cleared when your site’s content changes. Not using SpinupWP yet? <a href="https://spinupwp.com/pricing/" rel="nofollow ugc">Sign up here.</a>
Any Provider
We support DigitalOcean, Linode, AWS, and any other provider. If your server has an IP address, you can connect SpinupWP. It does need to be a fresh install of Ubuntu though.
Latest & Greatest Software
SpinupWP will install the latest stable versions of Nginx, PHP, MySQL/MariaDB, and Redis from the standard apt-get repos. No who-knows-what-they-did custom builds of packages. Disconnect from SpinupWP in the future and you can still keep your packages up-to-date with apt-get upgrade.
Automatic Security Updates
SpinupWP will configure your server to install security updates as soon as they are available to reduce the likelihood of a software vulnerability putting your server at risk.
Free SSL/TLS Certificates
Serving your site over HTTPS is essential these days, not only for security, but to take advantage of the performance improvements of HTTP/2 as well. When you add a site to SpinupWP, a free Let’s Encrypt SSL/TLS certificate will be acquired, installed, and configured for your site. And SpinupWP will handle certificate renewals as well, so you hardly need to think about certificates.
Cache All the Things
One of the keys to a great performing WordPress site is caching. All sites are set up with Redis object caching to greatly reduce database requests. And with the check of a box you can enable full-page caching to serve pages lightning fast without even hitting PHP.
Git Push-to-Deploy
Developers! Developers! Developers! Add a git repository to your SpinupWP site and simply push to master to deploy your code. GitHub, Bitbucket, or a custom git repo will work. You can also configure a build script to run some tasks on the server after deployment is complete.
Error Logs
WordPress doesn’t enable error logging by default. Probably because the log is saved to a publicly accessible directory and can quickly balloon to take up a lot of hard drive space. SpinupWP enables error logs by default but stores them in a safe place and makes sure they’re rotated regularly like other server logs.
Security Security Security
Each server provisioned by SpinupWP is security-hardened from the word go. SSH login is disabled for the root user (you login with your user and use sudo instead). The firewall only allows connections to Nginx and SSH and failed attempts are monitored and blocked when the reach a threshold. Nginx is configured to defend against XSS, clickjacking, MIME sniffing, and other attacks. Software security updates are installed automatically.
Scheduled Posts Published on Schedule
For every site you add via SpinupWP, a server-side cron job will be configured to make sure that your WordPress site’s cron is executed every minute, as it should be.
WP-CLI Preloaded
If you love WP-CLI (we do! ❤) you’ll be very pleased to find it available on the command line the first time you login to your server.
Security Isolation for Sites
For each site that you add to your server via SpinupWP, a new system user is created for that site. All site files are owned by the site user and a PHP-FPM pool is configured to run as that user as well. Each site only has access to its files and so if only one site has a security vulnerability and gets infected with malware for example, only the files for that one site can be infected.
SFTP Access for Your Clients
If you’re hosting a site for someone else, you can easily give them SFTP/SSH access to just that site. And because of the security isolation between sites, they will only have access to files for that site.
Professional Guidance & Best Practices
SpinupWP will actively point you in the right direction and offer suggestions for maintaining your server. And because it provides detailed feedback about the operations it runs on your server, you can learn what is happening with your server. New release of Ubuntu just came out, should I upgrade? We’ll add a notice to the app about that, why we don’t recommend upgrading your existing servers, and how you can spin up a new server with the new release of Ubuntu and migrate your sites to that server instead. Should I install Varnish to improve page caching performance? We’ve benchmarked Varnish and Nginx FastCGI Cache performed better. Varnish would add complexity too, so one less moving part is another reason. Much of the time SpinupWP will suggest things that you may not have even thought of. Email deliverability for example. SpinupWP will strongly encourage you to configure an email sending plugin for the best email deliverability. SpinupWP’s guidance is especially helpful for those new to managing a server, but can also help those who’ve been at it a while, providing transparency to our decisions.
Scheduled Backups of Site Files & Database
All server providers (DigitalOcean, Linode, etc) offer automated backups of your entire server for a fee. These services are great and we highly recommend having backups of your whole server. But what happens if some media or data was deleted by accident from your WordPress site? You’re not going to restore your entire server just to get that data back. That’s where site backups come in. Site backups are full backups of your site files (media, themes, and plugins) and database. They allow you to easily restore a single site or just some files or data from a single site. With SpinupWP’s site backups, you choose your preferred provider to stash your backups whether that’s Amazon S3, DigitalOcean Spaces, or Google Cloud Storage. You plug in your account details and SpinupWP will send your site backups there in an easy-to-see format.
Teamwork Makes the Dream Work
Create a new team account, invite a member of your team, and allow them to spin up their own servers. Or just only allow them to add sites, the permissions you give them is up to you.
<h4>Features</h4>
<ul>
<li>Page cache purging</li>
<li>Persistent object caching</li>
<li>Ensures debug.log files aren’t saved in a publicly-accessible location</li>
</ul>

The plugin is the perfect complement to one of the best, most well-crafted services I've used in years. I can't promote it enough. 

If I could write two reviews to give it 10 stars, I would.

I'm such a fan of the service at SpinupWP. 

Is it for everyone? Certainly not. You're far more "on your own" to deal with issues on your sites. 

But if you're comfortable enough to use a service like Digital Ocean, but not comfortable enough to be a full-on database administrator, SpinupWP fills a gigantic need in your life. 

Most importantly, keeping everything up to date is super mega simple, and explained in words I understand. 

SpinupWP is like having an expert looking over your shoulder

Incredible service

SpinupWP is a modern server control panel that's here to help you implement best practices for every server you spin up. Designed for WordPress.

Automattic

Donncha O Caoimh (a11n)

Mike Stott

Nauris

Mark (a11n)

Pete (a11n)

Adnan Haque (a11n)

Peter Petrov

This plugin generates static html files from your dynamic WordPress blog. After a html file is generated your webserver will serve that file instead of processing the comparatively heavier and more expensive WordPress PHP scripts.
The static html files will be served to the vast majority of your users:
<ul>
<li>Users who are not logged in.</li>
<li>Users who have not left a comment on your blog.</li>
<li>Or users who have not viewed a password protected post.</li>
</ul>
99% of your visitors will be served static html files. One cached file can be served thousands of times. Other visitors will be served custom cached files tailored to their visit. If they are logged in, or have left comments those details will be displayed and cached for them.
The plugin serves cached files in 3 ways (ranked by speed):
<ol>
<li>Expert. The fastest method is by using Apache mod_rewrite (or whatever similar module your web server supports) to serve “supercached” static html files. This completely bypasses PHP and is extremely quick. If your server is hit by a deluge of traffic it is more likely to cope as the requests are “lighter”. This does require the Apache mod_rewrite module (which is probably installed if you have custom permalinks) and a modification of your .htaccess file which is risky and may take down your site if modified incorrectly.</li>
<li>Simple. Supercached static files can be served by PHP and this is the recommended way of using the plugin. The plugin will serve a “supercached” file if it exists and it’s almost as fast as the mod_rewrite method. It’s easier to configure as the .htaccess file doesn’t need to be changed. You still need a custom permalink. You can keep portions of your page dynamic in this caching mode.</li>
<li>WP-Cache caching. This is mainly used to cache pages for known users, URLs with parameters and feeds. Known users are logged in users, visitors who leave comments or those who should be shown custom per-user data. It’s the most flexible caching method and slightly slower. WP-Cache caching will also cache visits by unknown users if supercaching is disabled. You can have dynamic parts to your page in this mode too. This mode is always enabled but you can disable caching for known users, URLs with parameters, or feeds separately. Set the constant “DISABLE_SUPERCACHE” to 1 in your wp-config.php if you want to only use WP-Cache caching.</li>
</ol>
If you’re not comfortable with editing PHP files then use simple mode. It’s easy to set up and very fast.
<h3>Recommended Settings</h3>
<ol>
<li>Simple caching.</li>
<li>Compress pages.</li>
<li>Don’t cache pages for known users.</li>
<li>Cache rebuild.</li>
<li>CDN support.</li>
<li>Extra homepage checks.</li>
</ol>
Garbage collection is the act of cleaning up cache files that are out of date and stale. There’s no correct value for the expiry time but a good starting point is 1800 seconds.
Consider deleting the contents of the “Rejected User Agents” text box and allow search engines to cache files for you.
Preload as many posts as you can and enable “Preload Mode”. Garbage collection of old cached files will be disabled. If you don’t care about sidebar widgets updating often set the preload interval to 2880 minutes (2 days) so all your posts aren’t recached very often. When the preload occurs the cache files for the post being refreshed is deleted and then regenerated. Afterwards a garbage collection of all old files is performed to clean out stale cache files. 
Even with preload mode enabled cached files will still be deleted when posts are modified or comments made.
<h3>Development</h3>
<ul>
<li>Active development of this plugin is handled <a href="https://github.com/Automattic/wp-super-cache" rel="nofollow ugc">on GitHub</a>.</li>
<li>Translation of the plugin into different languages is on the <a href="https://translate.wordpress.org/projects/wp-plugins/wp-super-cache" rel="nofollow ugc">translation page</a>.</li>
</ul>
<h3>Documentation</h3>
If you need more information than the following, you can have a look at <a href="https://github.com/Automattic/wp-super-cache/wiki" rel="nofollow ugc">the wiki</a> or the <a href="https://odd.blog/wp-super-cache-developers/" rel="nofollow ugc">Developer documentation</a>.
<h4>Preloading</h4>
You can generate cached files for the posts, categories and tags of your site by preloading. Preloading will visit each page of your site generating a cached page as it goes along, just like any other visitor to the site. Due to the sequential nature of this function, it can take some time to preload a complete site if there are many posts. 
To make preloading more effective it can be useful to disable garbage collection so that older cache files are not deleted. This is done by enabling “Preload Mode” in the settings. Be aware however, that pages will go out of date eventually but that updates by submitting comments or editing posts will clear portions of the cache.
<h4>Garbage Collection</h4>
Your cache directory fills up over time, which takes up space on your server. If space is limited or billed by capacity, or if you worry that the cached pages of your site will go stale then garbage collection has to be done. Garbage collection happens on a regular basis and deletes old files in the cache directory. On the advanced settings page you can specify: 
1. Cache timeout. How long cache files are considered fresh for. After this time they are stale and can be deleted. 
2. Scheduler. Setup how often garbage collection should be done. 
3. Notification emails. You can be informed on garbage collection job progress. 
There’s no right or wrong settings for garbage collection. It depends on your own site. 
If your site gets regular updates, or comments then set the timeout to 1800 seconds, and set the timer to 600 seconds. 
If your site is mostly static you can disable garbage collection by entering 0 as the timeout, or use a really large timeout value.
The cache directory, usually wp-content/cache/ is only for temporary files. Do not ever put important files or symlinks to important files or directories in that directory. They will be deleted if the plugin has write access to them.
<h4>CDN</h4>
A Content Delivery Network (CDN) is usually a network of computers situated around the world that will serve the content of your website faster by using servers close to you. Static files like images, Javascript and CSS files can be served through these networks to speed up how fast your site loads. You can also create a “poor man’s CDN” by using a sub domain of your domain to serve static files too.
<a href="https://wordpress.org/plugins/ossdl-cdn-off-linker/" rel="ugc">OSSDL CDN off-linker</a> has been integrated into WP Super Cache to provide basic CDN support. It works by rewriting the URLs of files (excluding .php files) in wp-content and wp-includes on your server so they point at a different hostname. Many CDNs support <a href="https://www.google.com/search?hl=en&q=%22origin+pull%22" rel="nofollow ugc">origin pull</a>. This means the CDN will download the file automatically from your server when it’s first requested, and will continue to serve it for a configurable length of time before downloading it again from your server.
Configure this on the “CDN” tab of the plugin settings page. This is an advanced technique and requires a basic understanding of how your webserver or CDNs work. Please be sure to clear the file cache after you configure the CDN.
<h4>REST API</h4>
There are now REST API endpoints for accessing the settings of this plugin. You’ll need to be authenticated as an admin user with permission to view the settings page to use it. This has not been documented yet but you can find all the code that deals with this in the “rest” directory.
<h4>Custom Caching</h4>
It is now possible to hook into the caching process using the add_cacheaction() function.
Three hooks are available:
<ol>
<li>‘wp_cache_get_cookies_values’ – modify the key used by WP Cache.</li>
<li>‘add_cacheaction’ – runs in phase2. Allows a plugin to add WordPress hooks.</li>
<li>‘cache_admin_page’ – runs in the admin page. Use it to modify that page, perhaps by adding new configuration options.</li>
</ol>
There is one regular WordPress filter too. Use the “do_createsupercache” filter 
to customize the checks made before caching. The filter accepts one parameter. 
The output of WP-Cache’s wp_cache_get_cookies_values() function.
WP Super Cache has its own plugin system, loaded before most of WordPress. Add your own plugin either by putting it in the wp-content/plugins/wp-super-cache-plugins directory, or by calling wpsc_add_plugin( $name ) with the full path to the plugin.
The cookies used to identify “known users” can be modified with wpsc_add_cookie( $name ) and wpsc_delete_cookie( $name ). See <a href="https://github.com/Automattic/wp-super-cache/blob/4cda5c0f2218e40e118232b5bf22d227fb3206b7/plugins/searchengine.php" rel="nofollow ugc">plugins/searchengine.php</a> as an example.
<h3>Troubleshooting</h3>
If things don’t work when you installed the plugin here are a few things to check:
<ol>
<li>Is wp-content writable by the web server?</li>
<li>Is there a wp-content/wp-cache-config.php ? If not, copy the file wp-super-cache/wp-cache-config-sample.php to wp-content/wp-cache-config.php and make sure WPCACHEHOME points at the right place.</li>
<li>Is there a wp-content/advanced-cache.php ? If not, then you must copy wp-super-cache/advanced-cache.php into wp-content/. You must edit the file and change the path so it points at the wp-super-cache folder.</li>
<li>If pages are not cached at all, remove wp-content/advanced-cache.php and recreate it, following the advice above.</li>
<li>
Make sure the following line is in wp-config.php and it is ABOVE the “require_once(ABSPATH.’wp-settings.php’);” line:
<pre><code>define( 'WP_CACHE', true );
</code></pre>
</li>
<li>Try the Settings->WP Super Cache page again and enable cache.</li>
<li>Look in wp-content/cache/supercache/. Are there directories and files there?</li>
<li>Anything in your php error_log?</li>
<li>If your browser keeps asking you to save the file after the super cache is installed you must disable Super Cache compression. Go to the Settings->WP Super Cache page and disable it there.</li>
<li>File locking errors such as “failed to acquire key 0x152b: Permission denied in…” or “Page not cached by WP Super Cache. Could not get mutex lock.” are a sign that you may have to use file locking. Edit wp-content/wp-cache-config.php and uncomment “$use_flock = true” or set $sem_id to a different value. You can also disable file locking from the Admin screen as a last resort.</li>
<li>Make sure cache/wp_cache_mutex.lock is writable by the web server if using coarse file locking.</li>
<li>The cache folder cannot be put on an NFS or Samba or NAS share. It has to be on a local disk. File locking and deleting expired files will not work properly unless the cache folder is on the local machine.</li>
<li>Garbage collection of old cache files won’t work if WordPress can’t find wp-cron.php. Check your access_logs for wp-cron.php entries and that your hostname resolves to the external IP address other servers on the network/Internet use.</li>
<li>If old pages are being served to your visitors via the supercache, you may be missing Apache modules (or their equivalents if you don’t use Apache). 3 modules are required: mod_mime, mod_headers and mod_expires. The last two are especially important for making sure browsers load new versions of existing pages on your site.</li>
<li>The error message, “WP Super Cache is installed but broken. The path to wp-cache-phase1.php in wp-content/advanced-cache.php must be fixed!” appears at the end of every page. Open the file wp-content/advanced-cache.php in your favourite editor. Is the path to wp-cache-phase1.php correct? This file will normally be in wp-content/plugins/wp-super-cache/. If it is not correct the caching engine will not load.</li>
<li>Caching doesn’t work. The timestamp on my blog keeps changing when I reload. Check that the path in your .htaccess rules matches where the supercache directory is. You may have to hardcode it. Try disabling supercache mode.</li>
<li>
If supercache cache files are generated but not served, check the permissions on all your wp-content/cache/supercache folders (and each of wp-content cache and supercache folders) and wp-content/cache/.htaccess. If your PHP runs as a different user to Apache and permissions are strict Apache may not be able to read the PHP generated cache files. To fix you must add the following line to your wp-config.php (Add it above the WP_CACHE define.) Then clear your cache.
<pre><code>umask( 0022 );
</code></pre>
</li>
<li>
If you see garbage in your browser after enabling compression in the plugin, compression may already be enabled in your web server. In Apache you must disable mod_deflate, or in PHP zlib compression may be enabled. You can disable that in three ways. If you have root access, edit your php.ini and find the zlib.output_compression setting and make sure it’s “Off” or add this line to your .htaccess:
<pre><code>php_flag zlib.output_compression off
</code></pre>
If that doesn’t work, add this line to your wp-config.php:
<pre><code>ini_set('zlib.output_compression', 0);
</code></pre>
</li>
<li>After uninstalling, your permalinks may break if you remove the WordPress mod_rewrite rules too. Regenerate those rules by visiting the Settings->Permalink page and saving that form again.</li>
<li>If your blog refuses to load make sure your wp-config.php is correct. Are you missing an opening or closing PHP tag?</li>
<li>Your front page is ok but posts and pages give a 404? Go to Settings->permalinks and click “Save” once you’ve selected a custom permalink structure. You may need to manually update your .htaccess file.</li>
<li>
If certain characters do not appear correctly on your website your server may not be configured correctly. You need to tell visitors what character set is used. Go to Settings->Reading and copy the ‘Encoding for pages and feeds’ value. Edit the .htaccess file with all your Supercache and WordPress rewrite rules and add this at the top, replacing CHARSET with the copied value. (for example, ‘UTF-8’)
<pre><code>AddDefaultCharset CHARSET
</code></pre>
</li>
<li>The error message, “WP Super Cache is installed but broken. The constant WPCACHEHOME must be set in the file wp-config.php and point at the WP Super Cache plugin directory.” appears at the end of every page. You can delete wp-content/advanced-cache.php and reload the plugin settings page or edit wp-config.php and look for WPCACHEHOME and make sure it points at the wp-super-cache folder. This will normally be wp-content/plugins/wp-super-cache/ but you’ll likely need the full path to that file (so it’s easier to let the settings page fix it). If it is not correct the caching engine will not load.</li>
<li>If your server is running into trouble because of the number of semaphores used by the plugin it’s because your users are using file locking which is not recommended (but is needed by a small number of users). You can globally disable file locking by defining the constant WPSC_DISABLE_LOCKING, or defining the constant WPSC_REMOVE_SEMAPHORE so that sem_remove() is called after every page is cached but that seems to cause problems for other processes requesting the same semaphore. Best to disable it.</li>
<li>Set the variable $htaccess_path in wp-config.php or wp-cache-config.php to the path of your global .htaccess if the plugin is looking for that file in the wrong directory. This might happen if you have WordPress installed in an unusual way.</li>
</ol>

WP Super Cache


I've been using this caching plugin since before Automattic took over management. Since I don't get very much in the way of comments on my site, the vast majority of hits are anonymous and don't change what should be on the page next time, so a static cache helps a *lot*.


Major speedup for the typical use case


It is very easy to use and optimally accelerates the website(s). Many thanks for the free version, it's simply brilliant.


Very helpful tool

A very fast caching engine for WordPress that produces static html files.

SpinupWP vs WP Super Cache