Yin’s Background Studio began as a refactoring task: replace a fragile, hard-coded random background selector with a native WordPress administration surface. The finished system stores multiple media-backed backgrounds in one option, supports static and random selection modes, handles reduced-motion fallbacks, previews images and videos, and validates manual sizing on both the client and server while preserving rollback at every deployment.

Technical environment

The implementation was developed on a small, resource-constrained WordPress server. At the time of the work, the confirmed…
Continue reading →

Migrating one old WordPress site can be unpredictable. Migrating four of them simultaneously—from an obsolete operating system, an old PHP runtime, aging themes, and years of accumulated plugins—requires a process designed around containment rather than optimism.

The goal of this migration was not simply to copy files onto a new server. It was to establish a clean, verifiable baseline:

• current WordPress core;
• PHP 8.4;
• Nginx and MariaDB on a modern Debian system;
• Cloudflare-proxied public HTTPS;
• the smallest practical active-plugin set;…
  Continue reading →

Weekly reporting often begins as a small manual task:

1. Open several analytics reports.
2. Change each report to the same weekly date range.
3. Wait for charts to load.
4. download each report as PDF.
5. Rename the files.
6. export supporting CSV data.
7. place everything in the correct folders.
8. verify that no report is missing or incomplete.

None of these steps is particularly difficult. The problem is repetition, inconsistency, and silent failure. This article describes the architecture and engineering decisions behind a macOS automation…
Continue reading →

Introduction

I recently faced a network configuration problem that initially looked simple:

How can I install V2Ray on a VPS when the only usable general-purpose public port is already occupied by qBittorrent?

The server was an Oracle Cloud Ubuntu VPS running qbittorrent-nox. Its WebUI was publicly accessible on TCP port 8080, while BitTorrent peer traffic used TCP and UDP port 47374.

Other candidate ports, including 80, 443, and 56894, were locally unused. However, external testing showed that they were not reachable through the Oracle Cloud network configuration. I did not want to modify the Oracle Virtual Cloud Network rules again, interrupt qBittorrent whenever I needed V2Ray, or expose unnecessary additional ports.

Continue reading →