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...