HOSTING TIPS ARCHIVE
October 2026 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.
42 guides, newest work first.
The data behind data-led design
Source health, content freshness, honest forecasts and separate site boundaries: the backend decisions that make data-driven maps, campaigns and creative useful.
The work is the qualification
Why I put more weight on working systems, practical judgement and years of hands-on learning than an AI certificate. Show the work and what it taught you.
MCP: from an AI prototype to a managed website
How MCP connects AI-assisted work to hosting, servers, WordPress and static builds, with ChatGPT Sites, Claude Artifacts and clear access boundaries.
How to contribute to WordPress and write a better plugin
A practical guide to WordPress and open source contributions: reproduce bugs, test patches, review well and build plugins people can install and trust.
AI vs the Exponential Time Hypothesis
OpenAI claims ETH is false. What was checked, why encryption is safe, and what I measured in my own code.
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.
Moving assets to a CDN? Keep your Web Workers at home
A 302 from /assets/ to a media host silently breaks Web Workers. Spot it in the console and with curl, keep worker files on the origin and purge the CDN.
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.
Check-then-set is a race: atomic locks in WordPress
Get-then-set locks, dedupe and balances break under concurrency. Fix them with SET NX, wp_cache_add, GET_LOCK or a ledger, and test with parallel wp eval-file runs.
When a benchmark win vanishes in production
A 3,000 times faster pre-check gave wrong answers on real data until it modelled the map edge. Model boundaries, check correctness and measure real inputs.
Get more from Cloudflare without making WordPress fragile
A practical Cloudflare setup for WordPress: cache boundaries, Turnstile, analytics, Varnish, Redis and honest measurements from TalkFuse and Sheffield Events.
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.
What a WordPress login lockout should actually do
Eight checks for a WordPress login lockout: count per account and per address, see the real IP behind Cloudflare, never reveal usernames, and never lock out the owner.
nginx or Apache: how to choose
When nginx is the better web server, when Apache is, how to run them together, PHP-FPM on both, migration gotchas and a short decision checklist.
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.
Welcome to the party, Endcliffe Park Café
Endcliffe Park Café is joining the AceMedia Host beta. Meet our first local café and see upcoming events in Endcliffe Park from Sheffield Events.
A simpler alternative to Dropbox and Google Drive
Could your hosting replace Dropbox or Google Drive for everyday file sharing? Explore AceHost workspaces and practical checks before moving your team’s files.
What to check before deleting old Lightsail backups
Check retention, exports, backing snapshots and a real restoration before deleting old Lightsail backups. Keep recovery evidence separate from availability.
Review AWS WAF costs without weakening protection
Separate AWS WAF rule, request, capacity and premium inspection costs. Check evaluation order and legitimate traffic before changing protection.
No-upfront AWS commitments: one year or three?
Compare one-year and three-year AWS commitments using eligible hourly usage, total liability and expiry. No upfront payment does not mean cancellable.
Why disabled AWS services can still cost money
Understand why disabled accelerators, idle public IPs and retained storage can still cost money, and what to check before retiring them.
An AWS bill review that leads to useful decisions
Review an AWS bill using a complete-month baseline, resource owners and practical checks. Separate estimated savings from changes that are safe to make.
Test WordPress forms through to email delivery
Check the whole enquiry journey, from validation and confirmation to the right inbox, so a working form does not hide a broken handover.
Serve photography galleries without heavy downloads
Keep photographs clear while reducing unnecessary downloads, with sensible image sizes, loading priorities and a recoverable publishing process.
Keep a Raspberry Pi development server responsive
Check power, cooling, storage, memory and background concurrency so a Raspberry Pi remains useful during real development work.
Diagnose Linux bottlenecks before changing settings
Use a small repeatable baseline to distinguish CPU work, memory pressure, storage waits and application queues before tuning a Linux web server.
Check hosting and tracking before rewriting falling content
Work out whether falling traffic points to a content problem, a broken page or missing measurement before you change your articles.
Check EC2 CPU credits and storage limits before resizing
Investigate burstable CPU capacity and both sides of the EBS connection, then change the resource that actually constrains the workload.
zram swap on a web server: setup, numbers and rollback
Swapping to a cloud disk can make MySQL and Redis wait hundreds of microseconds per page. zram swaps to compressed RAM instead. Setup, real numbers and rollback.
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.
Warm every cache variant you actually serve
A deployment can refresh the desktop page while a phone still receives an older cached copy. I make the warmer follow the same choices as real requests.
Running Varnish in front of a Redis page cache, without stale pages
Varnish and a Redis page cache can make WordPress very fast together, but only if they purge as one. The VCL and purge rules that keep both caches honest.
The first add to basket is a cache test
I test the moment an anonymous browser becomes a shopper with a basket. A fast cached product page does not prove that transition works.
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.
Move WordPress media off your server safely, then review its size
Plan WordPress media offload without broken images or exposed private files. Include CDN and backup costs, then measure before reducing server capacity.
Lock your origin server to Cloudflare with nginx
Proxying through Cloudflare only hides your server if the server refuses everyone else. How to lock an nginx origin to Cloudflare and stop visitors faking their IP.
Ten Linux server habits: disk, logs, updates, SSH and timers
Simple, repeatable checks for anyone running a Linux server: what is listening, what is filling the disk, automatic security updates, SSH keys, systemd timers and more.
Caching a WordPress block means keeping more than its HTML
A block can register scripts, styles and interactive state while it renders. I need those effects back on a cache hit too.
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.
No guides match those filters. Try another topic or reset the filters.