Awesome feedback @Unity. Thx for testing!
Yes! We missed to merge the feature-branch for this. v1.2.0 is now released and adds support for Unix sockets.
Thanks for pointing that out, it’s now sorted with a try/catch block.
Please do not hesitate to get back to us if anything is not as expected.
Just updated to v1.2.0 and confirmed Unix socket works perfectly here. Thanks for the quick fix!
Hi there!
MilliCache is about to take a big step forward with the upcoming 1.7.0 release. The full feature list is long, so here are just the highlights:
Cache Buckets
Store different versions of the same request, for example based on a request header. This is really handy with plugins like roots/post-content-to-markdown, where you want to cache and serve different responses for the same URL: HTML for humans, Markdown for AI. In MilliCache that’s a single rule.
Deduplication
Byte-identical responses are stored only once. MilliCache content-addresses each response body, so any requests that produce the exact same HTML (whether it’s /?foo and /?foo=bar, or two entirely different URLs) share a single stored copy in Redis. Less memory, same speed.
Metrics
You can now see how your cache is actually performing. On Multisite you also get network-wide stats.
Cache Health
There’s also a Status dashboard plus WordPress Site Health integration, so issues surface where you’d expect them and you won’t miss e.g. if your drop-in file is not in place.
Redis Replication & Sentinel support
MilliCache now supports high-availability Redis setups. For most sites we still recommend simply running Redis/Valkey on the host server, but larger projects that need a more resilient topology are now covered.
I’m very thankful that all the work bears fruit now and that MilliCache has got so many people excited. The feedback so far has been fantastic and I’m grateful for all the support, especially @ben for sharing it and writing it up.
composer require millipress/millicache:1.7.0-beta.4
And now we need your help again: please test 1.7.0-beta.4. There are so many different setups out there, and your feedback is exactly what makes a release this big ship smoothly. Bug reports, edge cases, weird configs: all welcome.
Hello! I tried updating to this but I keep getting this error message:
- Root composer.json requires millipress/millicache 1.7.0-beta.4 (exact version match), found millipress/millicache[dev-fix/cache-section-default-closed, dev-dependabot/npm_and_yarn/npm-dependencies-cfdadd46f4, dev-main, dev-next, dev-release-please--branches--next--components--millicache, dev-archive/pre-cleanup-2025-12, v1.0.0, ..., v1.7.0-beta.1] but it does not match the constraint.
Can’t see Millicache on WP Packages either:
Is this a problem in my chair or is it not possible to install anything after beta.1 with Composer at the moment?
Can you please try again? I’ve had to update Packagist, it didn’t automatically for the beta release.
Good! Thanks for your feedback.
PS. I noticed that the link here leads to a non-existent page:
Yes, it is not yet published and will be released with the final 1.7.0.
