andresmesi

Mesi Cache converts your WordPress site into a fully static HTML version served 
directly by Apache. Once a page is cached, it is delivered instantly without 
executing PHP or querying MySQL.
This design removes the need for PHP-FPM and database access on every visit, 
reducing server load to almost zero. The result is a pure static experience with 
instant page delivery and total control over your server resources.
Mesi Cache is minimalist, open, and transparent. It integrates cleanly with 
 .htaccess, uses no cron jobs, and requires no external services.
What it does 
* Creates static HTML files of posts, pages, categories and authors. 
* Serves files directly from disk, bypassing PHP and MySQL completely. 
* Invalidates relevant cache files when new content is published. 
* Allows manual cache generation and cleaning from the admin panel. 
* Works in root and subdirectory installations. 
* 100% local — no APIs, no remote calls, no external dependencies.
What it does not do 
* No CSS or JS minification. 
* No CDN integration (can be added manually). 
* No object or fragment caching. 
* No user/session-aware pages or dynamic content. 
* Does not serve cached content to logged-in users.
Mesi Cache focuses purely on static HTML delivery for public visitors. 
When cached, pages are served as plain files — no PHP or database code executes.
The plugin code is open, commented, and easy to extend. 
Developers can add features like preloading or CDN hooks using ChatGPT, Gemini, 
or manual edits.
<h3>License</h3>
This plugin is licensed under GPLv2 or later. 
You are free to use, modify, and redistribute it.

Mesi Cache

Ultra-light static HTML caching system for WordPress.

Viktor Szépe

“It’s important to make resources (images, scripts, stylesheets, etc.) cacheable.”
<a href="http://www.stevesouders.com/blog/2008/08/23/revving-filenames-dont-use-querystring/" rel="nofollow ugc">Steve Souders</a>
It is much easier to use a CDN without Query String Parameters. 
This plugins alters only local resources’ URL-s. 
The <code>ver</code> Query String Parameter will be inserted into the filename.
For example <code>jquery.min.js?ver=1.10</code> becomes <code>jquery.min.110.js</code>.
To reverse this in the web server add this line to your nginx config:
<pre><code>server {
 location ~ ^(.+)\.\d\d+\.(js|css|png|jpg|jpeg|gif|ico)$ {
 #try_files $uri $1.$2 /index.php?$args;
 try_files $uri $1.$2 =404;
 }
}
</code></pre>
Or to your Apache configuration or <code>.htaccess</code> file.
<pre><code>RewriteEngine On
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule ^(.+)\.\d\d+\.(js|css|png|jpg|jpeg|gif|ico)$ $1.$2 [NC,L]
</code></pre>
<h4>Testing the plugin before live usage</h4>
You can test the plugin by replacing the two <code>add_filter()</code> calls with this
<pre><code>require_once( dirname( dirname( dirname( dirname( __FILE__ ) ) ) ) . '/wp-load.php' );
wp();
echo o1_revving_src( $argv[1] ) . PHP_EOL;
</code></pre>
Then start it from CLI: <code>php revving.php <TEST-URL></code>
<h4>Links</h4>
Development of this plugin goes on on <a href="https://github.com/szepeviktor/resource-versioning" rel="nofollow ugc">GitHub</a>.

Resource Versioning

Turn Query String Parameters into file revision numbers.

Mesi Cache vs Resource Versioning