September 28, 2026
The mirror infrastructure made another solid jump forward tonight.
The new rack is assembled and loaded, Mirror Stack 1 remains our working reference stack, and the second mirror stack is now beginning to come online alongside it.
That matters because these machines will eventually be carrying real people’s websites, files, and services. The goal isn’t simply to have more servers running; it’s to avoid putting all of that data and capability in one machine or one physical location.
What We Got Done
Mirror Stack 1 is online and functioning as the reference build.
Its current layout is:
- 111 — Control
- 112 — WordPress Web
- 113 — Database / Mirror
- 114 — Community Server
Control 121 on Mirror Stack 2 is now online and reachable.
It is running Desktop Commander, and its software and service layout closely matches Control 111. That gives us the beginning of a second independently manageable mirror location rather than just another pile of hardware waiting to be configured.
We also confirmed that the networking between the stacks is working, including access from the Control servers to the separate IPMI management network.
In practical terms, that means the Control machines can reach and manage the servers behind them even when the operating system on one of those machines isn’t cooperating.
The other two machines for Mirror Stack 2 are alive as well. They’re still using their old .204 and .205 identities, but both respond through IPMI and will become:
- 122 — WordPress Web
- 123 — Database / Mirror
The eventual Community Server position for that stack is 124.
Cleaning Up the Addressing
We’re also correcting the home stack numbering so the entire system follows one understandable pattern.
The home stack will become:
- 101 — Control
- 102 — WordPress Web
- 103 — Database / Mirror
That gives us:
101 / 102 / 103 — Home
111 / 112 / 113 / 114 — Mirror Stack 1
121 / 122 / 123 / 124 — Mirror Stack 2
The numbering itself now tells us where a machine belongs.
The first digit identifies the general class of system: 1xx is the public-facing infrastructure, while 2xx is used for private systems such as Atoll, Harbor, and Ripper.
The second digit identifies the stack, and the third identifies the machine within it.
It’s a small organizational change, but as the number of systems grows, being able to look at 123 and immediately know where it belongs is going to save a lot of unnecessary detective work.
Already Mirroring the Website
The existing WordPress standby setup between 112 and the home web server is also already in place.
The website database, files, download assets, and supporting configuration can be copied between systems while machine-specific pieces—such as Cloudflare tunnel information—remain separate.
That’s an early working example of what the larger mirror design is supposed to accomplish: the same useful service available from more than one physical machine without treating every server as an identical clone.
Next
The next work is pretty straightforward:
finish moving the machines to their permanent addresses, verify Desktop Commander across the remaining systems, convert the former 204 and 205 machines into 122 and 123, and continue replicating the proven first mirror stack into the second.
It’s still infrastructure work, and there’s still plenty of testing ahead.
But the pictures tell the story pretty well tonight:
the racks are filling up, the stacks are talking to each other, and the second mirror location is starting to become a real system rather than a plan.