Actually, I have thought about blog sitemaps before (because I saw some experts have them on their websites, and they look awesome), but I was still a newbie at the time, and my mind was empty (even now, I encounter concepts I don’t understand every day and need to keep learning), and the articles at that time…

Preface With the official completion of the ten-part cloudflare series tutorial (these ten parts are equivalent to the main series, if there are more in the future, they can only be regarded as extra-partners, and it does not affect the fact that there are only ten parts in the main series~), I think I should also open a separate summary post for cloudflare: it will include the series tutorials and…

Introduction Because I have written several articles about the basics of AI before, I am thinking that it is time to release an AI learning map: first, I can sort out my thoughts and clearly know which knowledge points I have learned and practiced specifically, and it can also serve as my own AI learning notebook; second, it can also allow people who are destined to…

1 Introduction Since my blog uses a special WordPress active-active architecture (the macmini in the home data center is the primary write and secondary read node, and the VPS in Chicago Racknerd is the primary read node), once the macmini node has content changes (all blogs…

1 Introduction In the previous article (see: Home Data Center Series: Using X-WRT to Transform Retired Small Hosts: An Alternative Choice for Main Routers), I used an idle J2900 x86 small host to tinker with the soft router. It worked fine, the performance was more than adequate, and the system was stable...

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

1 Introduction Since I purchased Racknerd's VPS and completed the big project of moving the disaster recovery node from Tencent Cloud's lightweight server to Racknerd's Chicago VPS (see article: The second reconstruction of the home data center series blog architecture: service issues caused by VPS relocation...

1 Introduction Actually, I have always wanted to build a stable and pollution-free DNS service in the intranet, specifically to solve the DNS pollution problem, for some applications that only need to solve DNS pollution, such as emby's tmdb plug-in, which cannot scrape film and television information normally, just because its A...