simon.holliday

<p>FlexiCache is a fast, full-featured and flexible caching system which will improve the performance and availability of any WordPress site.</p>
<p>It is highly configurable to allow unlimited caching rules – expiring different pages at different times, not caching some pages at all, caching multiple versions of the same page depending on browser, language, and so on.</p>
<p>FlexiCache will also work straight out of the box without any need for complex configuration.</p>
<h4>Features</h4>
<ul>
<li>Extensively configurable using user-defined conditions</li>
<li>Handling of high-traffic periods where multiple clients may simultaneously request uncached or expired items</li>
<li>Standalone mode which bypasses WordPress and third-party theme and plugin code to serve cached pages faster</li>
<li>Choice of storage engines: Filesystem, Memcache and SQLite</li>
<li>Pre-caching functionality to cache new versions of pages before the existing ones expire</li>
<li>SQLite indexing of Filesystem and Memcache stores to speed up removing specific items from the cache (automatically enabled if SQLite is available)</li>
<li>Sends appropriate HTTP cache headers to the requesting client</li>
<li>Serves files in compressed formats accepted by the requesting client</li>
<li>Compatible with WordPress MU</li>
</ul>
<h3>Upgrading FlexiCache</h3>
<p>FlexiCache stores config and cache data within the plugin directory (see plugin documentation in versions 1.2.4.2 onwards for the reason why).</p>
<p>If you upgrade the plugin using WordPress’s built-in upgrade process, the entire plugin directory will be replaced, including your config and cache data.</p>
<p>To preserve these, take a copy of the “plugins/FlexiCache/_data” directory before upgrading, and then copy it back after the upgrade is complete.</p>
<p>If you upgrade directly via SVN, this should not be required, since only the files under version control will be updated.</p>
<h3>Deactivating FlexiCache</h3>
<p>FlexiCache can be disabled via the admin interface as with any plugin, however if you are running in Standalone mode, you should remove the .htaccess modifications before deactivating the plugin.</p>
<p>For a standard WordPress install, this modification can be done via the admin interface, however it is recommended that you make this change manually, especially if using WordPress MU, where multiple sites may share the same .htaccess file.</p>
<p>Please see the documentation supplied with the plugin (accessible via WordPress’s admin interface) for more information.</p>


FlexiCache

FlexiCache is a fast, full-featured and flexible caching system which will improve the performance and…

Jon Otaegi

<p>This simple plugin creates a <code>/health</code> endpoint to let you monitor the status of your WordPress website. The endpoint tests the status of your database connection and returns a <code>200 OK</code> HTTP status code while your page is healthy. You can read more on HTTP status codes at the <a href="https://en.wikipedia.org/wiki/List_of_HTTP_status_codes" rel="nofollow ugc">Wikipedia article</a>.</p>
<p>External tools such as website monitoring services can access the exposed endpoint at regular intervals. This can help you verify that your WordPress website is performing correctly.</p>
<p>You can find more information about the <a href="https://docs.microsoft.com/en-us/azure/architecture/patterns/health-endpoint-monitoring" rel="nofollow ugc">Health Endpoint Monitoring Pattern</a> at the <a href="https://docs.microsoft.com/en-us/azure/architecture/patterns/" rel="nofollow ugc">Microsoft Azure Documentation</a> website.</p>
<h4>Development</h4>
<p>This plugin is being developed on <a href="https://github.com/jonotaegi/wordpress-health-endpoint" rel="nofollow ugc">GitHub</a>. If you want to collaborate, feel free to submit pull requests or report bugs on the issue tracker.</p>


Health Endpoint


Security utilities complain the plugin is abandoned.


Update the version number!

Creates a /health endpoint that returns a 200 OK HTTP status code while WordPress is performing correctly.

FlexiCache vs Health Endpoint