From an IKEA Cabinet to a Mini Rack: u/pablokbs’s Home Server Story

Eva Wong is the Technical Writer and resident tinkerer at ZimaSpace. A lifelong geek with a passion for homelabs and open-source software, she specializes in translating complex technical concepts into accessible, hands-on guides. Eva believes that self-hosting should be fun, not intimidating. Through her tutorials, she empowers the community to demystify hardware setups, from building their first NAS to mastering Docker containers.

Thank you to u/pablokbs for sharing a cabinet conversion that brings everyday home services into one manageable space. The project combines Raspberry Pi boards, a ZimaBoard 2 and an e-ink display inside an existing IKEA cabinet. Its appeal is practical: organize useful equipment around the place it already occupies, then make the installation easier to understand and maintain.

The Self-Hosting Day contribution describes moving from a dusty, untidy cabinet to a printed mounting arrangement compatible with 10-inch rack models. The story below keeps the contributor's reported equipment separate from the general operating guidance drawn from the linked project documentation.

The Cabinet Was the Starting Point

The creator measured an approximately 11-inch-wide cabinet, removed its door and printed guides for the sides. Reusing the furniture set the physical constraint before the mounting parts were chosen.

For readers considering a similar conversion, the useful first step is to describe access as well as fit. A device needs room for its connections, and a storage drive may need to be removed without dismantling the whole arrangement. A shelf that accepts an enclosure can still be awkward to service once power and network cables are attached. Those are planning questions for a new build, not measurements supplied for this cabinet.

The nearby comparison is our seven-inch desktop homelab story. That creator chose a compact rack first; this contribution began with existing furniture. Both make the physical constraint visible before discussing applications.

The creator’s original IKEA cabinet conversion, with the mini rack and e-ink display.
The creator’s original IKEA cabinet conversion, with the mini rack and e-ink display. Source: u/pablokbs.

Each Computer Has a Recognizable Household Role

Reported equipment Examples of its assigned work
Raspberry Pi 5 Pi-hole, monitoring and the TRMNL-related software
Raspberry Pi 4 Home Assistant
ZimaBoard 2 with two 4 TB WD Red Plus drives Media applications, remote access and network services
TRMNL White display and a UPS A custom information page and power support

A role map remains useful even when one machine runs several applications. It should explain which service a household uses, which computer provides it and which data it needs. A list of installed containers answers a different question: what software exists. The two records can complement one another, but an app list alone does not explain how to recover an interrupted household task.

Keep that map short enough to update after moving a workload. A service that changes hosts needs its saved address, configuration path and any shared storage relationship reviewed. The goal is an installation the owner can explain without reconstructing every decision from memory.

Two DNS Installations Still Need a Deliberate Client Configuration

Pi-hole's post-install documentation explains how clients are directed to the DNS service, commonly through router-provided settings or individual client configuration. Installing the software and making devices use it are separate steps. A running dashboard does not establish which resolver a television or phone actually contacts.

When planning more than one DNS instance, check the addresses distributed to clients and the behaviour of an ordinary lookup. The presence of two machines should not be described as tested failover unless that behaviour has actually been demonstrated. Configuration consistency and client behaviour need their own checks; neither follows simply from counting installed instances.

A useful maintenance note records the intended resolver addresses and how to reach a machine directly during a DNS interruption. Keep those notes available without relying entirely on the service being repaired. This is a general operating habit, rather than an additional feature claimed for the contributor's setup.

Home Automation Deserves Its Own Recovery Record

Home Assistant's backup guidance covers backup contents, schedules, destinations and the encryption material needed for restoration. The important distinction is between creating a backup and retaining a copy somewhere accessible after the original system fails. An archive that exists only on the affected device may be difficult to reach when needed.

For a household installation, write down the chosen backup destination and preserve the recovery information separately. Review what the backup includes before assuming that every media folder or other large directory is covered. Where encryption is used, a retained archive and the means to unlock it are both part of the recovery plan.

The official settings example below illustrates those choices. It does not show the contributor's configuration, and this account does not establish their backup schedule or a measured restore time.

Official Home Assistant example showing backup locations and encryption options; not the contributor’s installation.
Official Home Assistant example showing backup locations and encryption options; not the contributor’s installation. Source: Home Assistant documentation.

An E-Ink Display Can Make Status Easier to Notice

TRMNL's BYOS documentation describes pointing a device at a self-hosted server implementation. That helps distinguish the display from the service supplying its content. A visible page is the output of a chain that still includes data collection, rendering and delivery to the screen.

When choosing information for a household status page, decide what a person should do after seeing it. A temperature can be useful context; a maintenance notice might need a clear date and expected interruption. A page that requires the administrator to explain every value is serving a different purpose from a quick household overview.

Also distinguish a displayed value from a fresh reading. If the display is used to communicate service health, include a way to understand when its information was updated. This is a design consideration for readers, not a claim that the photographed page implements a particular refresh or alert policy.

A UPS Adds Time, While Shutdown Behaviour Needs Its Own Plan

The Network UPS Tools overview separates communication with power hardware from monitoring clients that can respond to its state. Where compatible equipment and configuration support it, that distinction provides a framework for coordinated shutdown. Plugging devices into a battery supply does not by itself document how their operating systems will react.

For a cabinet with several computers, identify which devices need to remain powered together and how they will stop if an interruption continues. Runtime depends on the connected load and the battery, so it should be measured for the actual installation rather than inferred from the cabinet's small size. The original contribution does not provide an outage-runtime measurement.

FAQ

Does fitting a rack model guarantee that it fits any cabinet?

No. Width is only one constraint. Depth, cables, access and the mounting arrangement also need to be checked against the furniture and equipment actually being used.

Do several small computers automatically provide redundancy?

No. Service dependencies and client behaviour determine what remains available. Multiple devices can still depend on the same power supply, switch or storage location.

Is the backup settings image from the contributor?

No. It comes from Home Assistant's official documentation and is labelled as an example. The cabinet photograph is the contributor's original image.

Should everything move into one operating system?

Only if that solves a concrete problem. The contributor's role-based arrangement shows why separate machines can remain useful. Evaluate maintenance and recovery before combining workloads.

Conclusion

This cabinet conversion makes a familiar home-server problem tangible: equipment can work individually while remaining difficult to manage as a group. Giving the hardware a deliberate home and describing each role helps connect the physical arrangement with the services people use.

Our small homelab community story offers another perspective on keeping responsibilities clear. Whether the enclosure is a cabinet or a rack, the useful next step is the same kind of clarity about access, maintenance and recovery.

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

Get More Builds Like This

Stay in the Loop

Get updates from Zima - new products, exclusive deals, and real builds from the community.

Stay in the Loop preferences

We respect your inbox. Unsubscribe anytime.