Thank you to u/Trousers_Rippin for sharing a compact ZimaCube and ZimaBoard setup built around daily use. One machine holds most applications; the other keeps smart-home services separate. The result is a household server arrangement where an experiment does not have to interrupt the lights.
The original Reddit story appeared in August 2024. This is an account of the original hardware generation, with Debian and Docker chosen by its owner. The cabinet photograph and application dashboard show how much functionality can sit behind a relatively modest physical setup.
A Household Problem Determines the Second Server's Job
The owner's detailed follow-up explains the reason for separating home automation: tinkering on the shared machine had previously interrupted lighting. Keeping an existing smaller computer for that role gave everyday home functions their own place.

That is an effective way to evaluate a second server. The first question is which service needs a different maintenance window. A media application can usually tolerate an owner testing a new configuration at a convenient time. A household relying on automated lighting may have a different expectation.
Physical separation makes that distinction easier to act on. It does not remove shared dependencies such as power and networking, but it lets the owner work on one operating system without deliberately rebooting the other. The value comes from the responsibility assigned to each host.
The Two Machines Share an Operating Approach
| Component | Owner-reported configuration or role |
|---|---|
| ZimaCube Personal | N100, 16 GB RAM, 256 GB storage; majority of applications |
| ZimaBoard 832 | N3450, 8 GB RAM, 32 GB storage; smart-home services |
| Software on both hosts | Minimal Debian 12 and Docker |
| Household DNS | A Pi-hole instance on each server |
| Application overview | Homepage dashboard |
The hardware references for this story are the original ZimaCube Personal Cloud and original ZimaBoard server. Keeping those generations explicit helps readers interpret a historical user build without substituting a newer product's specifications.
A shared operating approach can reduce the number of different administration methods one person needs to remember. It also leaves a useful opportunity for documentation: record each host's role alongside its service definitions. Similar software on two machines should not make it unclear which one owns an important task.
Our small homelab story from u/jc-21 explores another arrangement of compact machines with defined jobs.
A Single Dashboard Makes the Service Collection Legible

The screenshot is organized around activities. It places management tools in one column, everyday utilities in another, and monitoring beside media applications. This gives the application collection a structure a person can scan before deciding what to open.
The Homepage service configuration documentation explains groups and individual service entries. For a reader designing an overview, that is a useful starting point: group services according to the decisions the page should support.
A service directory and a host inventory serve different purposes. A dashboard can help find a media library or monitoring page, while a maintenance record identifies the machine and storage behind it. Keeping both makes it easier to understand why one application has stopped without assuming every service on the page shares the same failure.
The image is also a snapshot from the original post. It illustrates the owner's organization at that point in time; it should not be read as a live availability report or a promise that every displayed integration will behave identically in a new installation.
Smart-Home Containers Have a Different Everyday Audience
The owner identifies Home Assistant, Mosquitto and Zigbee2MQTT among the smart-home containers, with a SONOFF Zigbee USB adapter. That places the second machine close to routines that other people in the house experience directly.
For a similar project, maintenance planning starts with that audience. A person using a light switch should not need to know which experimental container is being rebuilt elsewhere. Separating household services gives the operator a reason to schedule changes deliberately and keep a recovery path for the configuration.
The Docker guide to persistent volumes explains storage that can survive the removal of a container. Applied to a home server, the practical question is where the application keeps the information that makes it useful: settings, databases and other persistent state.
Recreating a container and recovering a household service are therefore different milestones. A reader should be able to locate that state and explain how it would be restored before assuming an application definition is enough.
Two DNS Instances Still Need a Network Plan
The Pi-hole documentation describes DNS-based blocking on the owner's own hardware. In a two-host arrangement, DNS deserves attention because a service may be running normally while clients struggle to reach it by name.
For readers adopting a similar design, two installations are only part of the picture. The useful verification is to check which DNS addresses clients receive and then observe resolution while one server is unavailable. That would test the actual household configuration rather than infer behavior from the number of machines.
The Pi-hole-to-family-server story offers another example of a small network service becoming part of a broader home-server routine.
Storage and Noise Remain Separate Design Decisions
In the follow-up, the owner describes four 3 TB hard drives in RAID 0, with copies on external drives. The opening post's approximate long-term-storage figure should not be substituted for an independently measured usable-capacity result.
The important planning question is recovery. A storage layout that provides access to files still needs a way to recover those files and their applications. A useful record would identify which content is copied, when that copy runs, and how an owner would use it after a failure.
The owner also reports replacing the Cube's fans with Noctua units and being pleased with the quiet result. That is a personal impression, without sound-pressure or temperature measurements. For another cabinet installation, the relevant observations would include airflow, drive temperatures and noise in the actual room.
FAQ
Is this a ZimaOS installation?
No. The owner chose Debian 12 and Docker. The dashboard is Homepage.
Does the second computer establish automatic failover?
The source describes separated responsibilities. It does not document a clustered failover system.
Does the drive arrangement provide redundancy?
The owner explicitly identifies RAID 0, which does not provide drive redundancy. External copies are a separate part of the reported arrangement.
Can the fan replacement be reproduced from this post?
The post reports the result but does not supply a complete installation procedure or measured validation.
Conclusion
The useful lesson in this compact setup is the maintenance boundary. Give everyday household functions a clear home, organize applications so they are easy to find, and keep the underlying machines and data understandable. A small physical footprint can still support a considered division of responsibility.
Welcome to the ZimaSpace community! Share your setup, ask questions, and explore practical build guides, real user stories, and product updates with fellow self-hosters.
Zima Campaign Hub
More to Read

A ZimaBoard 2 Prototype with Two 22 TB Drives on the Test Bench
Explore sabitech2k’s early ZimaBoard 2 drive test, the reported power conditions, and the existing ZimaBoard used for Proxmox backups.

A LEGO Rack for a First ZimaBoard 2 Home Server
See how a first-time builder organized a ZimaBoard 2 and two SSDs in a LEGO rack, with Home Assistant and home-office storage planned next.

A ZimaOS NAS and Proxmox Homelab Under a TV, Below 14 cm Tall
PierroDuv separates a custom ZimaOS SSD NAS from a Proxmox mini PC under a TV shelf, with reused parts, low clearance and clearly divided...


