HOSTING TIPS ARCHIVE
PHP: hosting guides
Practical steps and checks for hosting, WordPress and performance. Browse a topic or use the dates to explore the experience behind the advice.
16 guides, newest work first.
PHP 8.6 for WordPress: compatibility checks
What I check before moving WordPress to PHP 8.6: plugin and extension compatibility, Redis formats, OPcache memory, background jobs and a tested rollback.
PHP 8.6: new features and upgrade guide
PHP 8.6 new features explained: Duration, clamp, callbacks and polling, plus compatibility, support dates and practical checks before upgrading.
Invalidate a Redis cache without scanning it
Clearing 100,000 Redis keys took 2.4 s with SCAN and DEL, 0.26 s with batched UNLINK and one command with a generation counter. Code and trade-offs.
Four clock bugs that hide in scheduling code
Lost UTC offsets in British Summer Time, mismatched day buckets, drifting "last Friday" rules and midnight wraps: symptoms, tests and fixes.
PHP2Shell: what happened, and what I did
Two critical PHP flaws leaked a day early and were attacked within hours of the fix. Here is the public picture, how to check your own server and what I did.
Keep PHP up to date and why it matters
PHP fixes only protect you once the PHP actually serving your site is running them. Here is how I keep that under control.
Critical PHP security release: what was fixed and what I did
PHP released fixes on 21 October for two critical remote code execution flaws. This is what changed and what I did.
Self-hosted WordPress: eight WP-CLI checks for speed and safety
Eight practical checks for WordPress on your own server: verify core files, run cron properly, find autoload bloat, lock down editing, use an object cache and update with a way back.
Test deployments as the web server user
A release can pass checks in an administrator’s shell and still fail for the account which serves the shop. I check both the runtime and its access.
Atomic deploys with automatic rollback for PHP and WordPress
Release folders, a symlink swap that is truly atomic, rollback when a post-deploy step fails, and the OPcache and permission traps that catch people out.
Apache tuning and hardening: PHP-FPM, HTTP/2, caching and Cloudflare IPs
Practical Apache tips: switch to the event MPM with PHP-FPM, turn on HTTP/2 and Brotli, cache static files properly, read real visitor IPs behind Cloudflare and hide what should be private.
Deployment configuration needs one clear owner
Define which source owns each deployment configuration file, then test that old local copies cannot silently override an intended change.
Test the oldest PHP version your site actually runs
A clean local lint is useful, but I also check the runtime that receives the deployment.
PHP in the browser and PHP in cron must agree on the cache
The same cache key is not enough. Every process that reads it has to understand the value written underneath it.
A slow cache should not hold the whole site hostage
I put a time budget around Redis so that a temporary cache problem does not quietly occupy every PHP worker.
Keep a rollback route when moving PHP
I move the web server onto a separately tested PHP runtime, keep a clear route back, and check cron and background work as part of the change.
No guides match those filters. Try another topic or reset the filters.