HOSTING TIPS ARCHIVE
Operations: 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.
20 guides, newest work first.
Cron locks stop overlapping runs. Make sure they do not hide skipped ones
Per-site flock locks stop scheduled WordPress runs stacking up. Why I removed a shared lock, and how a background lease skipped thousands of runs unnoticed.
Audit the tipping record before anyone sees the headline number
A tipping record's profit figure looked good. A settlement audit found tips matched to the wrong race. What went wrong, and why waiting is an honest state.
A development site that never calls the outside APIs itself
A development site reads only what production has cached, through a restricted SSH tunnel, so testing never spends quota or gets the server blocked.
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.
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.
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.
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.
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.
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.
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.
Show what your monitoring has actually checked
Make the scope, age and missing evidence visible in a hosting status summary, so a reassuring label has something useful behind it.
Test that your Git backups can be restored
Check what a repository archive includes, verify it and practise restoring it before relying on it for recovery.
Check the Apache configuration that is actually loaded
Before changing an Apache limit, I trace the running service to the configuration it reads. A plausible file in the right directory can still be inactive.
No guides match those filters. Try another topic or reset the filters.