1 Preface In my previous multi-active architecture deployment practice (see details: Home Data Center Series - WordPress Multi-Active Architecture (Simplified Version) Implementation Plan in Personal Blogs), Cloudflare's Health Checks were used to achieve node...
1 Preface In previous articles (see: Home Data Center Series: Making WordPress Sites Static via Simply Static Plugin), I introduced in detail how to use Simply Static on WordPress ...
1 Background Introduction The fundamental trigger that initially gave rise to the idea of setting up a WordPress multi-active solution was actually very simple: that time my home was disconnected by Telecom for a full 3 days without any warning (see article for details: Home Data Center Series: Talking about Current Personal Blogs from This Home Disconnection...
1 Preface Since my blog adopts a special WordPress active-active architecture (the Mac mini in the home data center is the primary-write/secondary-read node, and the Chicago Racknerd VPS is the primary-read node), once there is a content change on the Mac mini node (all blogs...
1 Preface In the previous article (see: Home Data Center Series: Transforming a Retired Mini PC with X-WRT: An Alternative Choice for Main Router), I used an idle J2900 x86 mini PC to tinker with a software router. It ran fine, with performance to spare and a stable system...
1 Preface The main router of my home data center has always been iKuai. Its main advantage is supporting multi-dialing (for the detailed concept of multi-dialing, see the article: ). Since my home Telecom broadband supports up to 3 dials, I can obtain 3 public IPv4 addresses simultaneously, which for someone like me with multi-line access...
1 Preface When deploying a WordPress multi-active node solution, a crucial technical point is read-write separation: that is, routing all operations involving "writing to the database" (such as publishing articles, modifying content, modifying plugin configurations, submitting comments, etc.) to the primary-write node, while other nodes...
1 Preface I have always wanted to build a synchronously updated static copy for my WordPress-based dynamic blog. On one hand, it is out of the pursuit of "full-site caching" and "always online" capabilities—after all, in the early days, the blog had not implemented disaster recovery and active-active deployment, and WordPress itself...
1 Preface Previously, I wrote an article about dnscrypt-proxy deployment (see: dnscrypt-proxy (v2.1.8) Multi-Scenario Configuration Guide: From Upstream Deployment to Downstream Integration). The architecture at that time was: utilizing Racknerd...
1 Introduction My previous blog architecture was a home data center (master node + hot standby node) + Tencent Cloud (disaster recovery node), which is a typical "single-node read/write" scheme. Since only the master node handles database read and write requests on a daily basis, real-time synchronization between databases is not required: whenever...