1 Introduction I have always used iQuick as the main router in my home data center. Its main advantage is that it supports multi-dial function (for the detailed concept of multi-dial, please refer to the article:). Because my home telecom broadband supports up to 3 dials, I can obtain 3 public network IPv4 addresses at the same time, which is very useful for people like me who have multiple line access...

1 Introduction When deploying a WordPress multi-active node solution, a crucial technical point is read-write separation: that is, all operations involving "writing to the database" (such as publishing articles, modifying content, modifying plugin configuration, submitting comments, etc.) are uniformly routed to the primary write node for completion, while other nodes...

1 Introduction I have always wanted to build a synchronously updated static copy for a dynamic blog based on WordPress. On the one hand, it is out of the pursuit of "full site cache" and "always online" capabilities - after all, early blogs have not yet achieved disaster recovery and dual-active deployment, and WordPress itself...

1 Preface Before, 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: using Racknerd…

1 Introduction My previous blog architecture is a home data center (master node + hot standby node) + Tencent Cloud (disaster recovery node), which is a typical "single node read and write" solution. Since only the master node is responsible for processing database read and write requests on a daily basis, there is no need for real-time synchronization between databases: every time...