Writing
DevOps/SRE/Platform Engineering with a side of questionable architectural decisions
Latest Post
How to guide on checking if your Magento 2 store is safe from the Session Reaper (CVE-2025-54236) exploit. And guidance on how to patch and secure your site if it is not.
Approaches to simply deploying patches across a large inventory of Magento 2 deployments
Ever found yourself wondering why a store required downtime to deploy? Or even the case where `setup:db:status` constantly reports `Declarative Schema is not up to date` despite you just update it?
After 12 months running self-hosted Sentry in production: £2,500–£3,500/month saved vs cloud, stable enough to mostly forget about, but disk management is the ongoing pain point.
Delaying Magento 2 full page cache purges to a set schedule, to improve frontend performance and reduce system load during busy periods such as sales events like black friday.
Should you aim for 100% uptime across your servers? Or instead target fluid infrastructure where short lived nodes can spawn and die as required?
Do you employ Chaos Engineering with your Enterprise scale stores? Where is why you should start restarting services and infrastructure at random.
Have you explicitly disable the Magento 2 setup route in your web server configuration? The vast majority of sites scanned are showing this route as leaking your full Magento Version.
Quick reference guide to debugging Varnish usage within Magento 2, covering cache utilisation, hit & miss rate logging, identifying the source of purge requests