Thank you to u/AppointmentDue4923 for sharing a small homelab that began with Minecraft for friends. A Raspberry Pi was the first server; a Lenovo ThinkCentre M720q later became the main node as the project expanded to websites, media and household services. The original white-rack photograph shows how that growth became a physical installation.
In the Self-Hosting Day contribution, the creator describes using both CasaOS and ZimaOS. The story has a clear progression: a game created the initial need, a stronger main machine followed, and services for family and friends gave the lab more work to do.
Minecraft Supplied a Reason to Start
The original purpose was to host a Minecraft server for the creator and their friends. A Raspberry Pi was enough to begin learning how to make that shared space available. It gave the project a user group before there was a finished rack or a wider service inventory.
The creator says the server grew to more than fifty players. That describes the community’s growth in the account, not a measured result showing fifty simultaneous players on a specified Pi configuration. The distinction keeps an engaging part of the story from turning into a misleading hardware promise.
A game server also introduces a particularly tangible kind of retained data: a world that people have spent time building. For another household project with Minecraft among its everyday services, see the Pi-hole-to-family-server account. The applications can start small while the value of the saved state grows.
The ThinkCentre Became the Main Node
| Equipment | What the creator identifies |
|---|---|
| Lenovo ThinkCentre M720q | The main node after the earlier Raspberry Pi stage |
| Raspberry Pi 5 | An 8 GB machine in the current hardware inventory |
| FritzBox 7590 AX v2 | The listed home router |
| Cisco five-port switch | Obtained through school; not in the rack at the time of the account |
| SATA SSDs and HDDs | Additional storage connected using USB adapters |
| CasaOS and ZimaOS | Both used for the creator’s servers |
The move to a ThinkCentre changes the main compute platform without erasing the Pi’s place in the project. The post does not give the M720q processor, memory or a service-by-service map, so the hardware list should not be expanded using the specifications of another person’s similar model.
The operating-system detail deserves the same care. CasaOS and ZimaOS are both named, but the contribution does not assign an operating system to every device. It is enough to describe the software used across the lab without inventing which machine hosts each individual application.

Hosting Websites Added Another Group of Users
The creator now runs websites built for their father and some of his friends. That addition gives the lab a second shared purpose beyond the game server. The machine has become useful to people who may care about a working website more than the hardware or container platform behind it.
Nginx Proxy Manager and Cloudflared appear in the service list alongside Crafty, Jellyfin, Nextcloud, Home Assistant and AdGuard Home. Those names describe access, game administration, media, files, automation and filtering. They should not be collapsed into a claim that one tool performs every network or storage function.
For readers studying the access layer, the Nginx Proxy Manager project explains its proxy-management interface. A hostname, its destination and the application behind it remain separate things to document when a website or service moves to another machine.
Game Administration and Game Recovery Are Related Tasks
Crafty is listed as the controller for Minecraft. Its official documentation provides the administration reference, while the server backup manager guide covers a particular part of operating a game server.
That separation helps explain what a growing game service needs. Starting the process, managing files and preserving a recoverable world are connected responsibilities, but a working dashboard alone does not demonstrate the recovery result. The contribution does not publish a backup schedule or a restore test.
The practical next step for another builder is to identify the world data and the settings needed to reopen it, then test a recovery separately from the live game. Keep the original working world available while developing the procedure. That makes a hardware move easier to evaluate through the players’ actual experience.
The Small Rack Organizes Hardware Without Ending the Project
The photograph shows a compact white arrangement with the ThinkCentre, connection panels and drive carriers. It is useful evidence of how the equipment was brought together. The post does not supply enclosure model files or a complete construction guide.
The creator also says capacity is becoming tight again. Several SATA drives are connected over USB adapters, so the physical storage arrangement is part of the next planning decision. The source does not identify a measured USB bottleneck, a particular RAID layout or the cause of every capacity constraint.
There is a physical parallel with the IKEA-cabinet mini rack: the enclosure makes a collection of small devices easier to organize, while applications continue to create new requirements. A finished-looking rack can still contain a system that is changing.
Readers comparing compact x86 options for a future node can review the ZimaBoard 2 specifications alongside their current ports, drive connections and workload needs. In this contribution, the actual main node remains the ThinkCentre, with ZimaOS forming part of the lab’s software experience.
FAQ
Is this a ZimaOS user story?
Yes. The creator explicitly names CasaOS and ZimaOS among the software used for their servers. The hardware inventory includes a ThinkCentre M720q and a Raspberry Pi 5.
Does the player figure establish simultaneous Minecraft capacity?
No. It is a description of growth supplied by the creator, without a concurrency test, game-version details or workload measurements.
Which machine runs each application?
The contribution identifies the main node and lists services across the setup, but it does not map every application to an individual machine or operating system.
Is the Cisco switch visible in the current rack?
The creator specifically says it was not in the rack at the time of the post. The hardware list and the photograph should be read with that distinction intact.
Does the post document a complete storage or backup design?
It mentions SATA drives connected using USB adapters, but does not provide a full storage topology or a completed restore exercise. Use the ZimaOS storage and backup guides and application-specific instructions when planning those responsibilities.
Conclusion
AppointmentDue4923’s lab began with a game for friends and gradually gained a main x86 node, websites for other people and a broader service collection. The original rack photograph gives that progression a recognizable form without suggesting that the project has stopped growing.
The useful thread is the relationship between the equipment and the people using it. A Minecraft world, a family website and a shared file collection each give the next upgrade a reason, while their data and access requirements help determine what the server needs to do next.
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 Quiet ZimaCube and ZimaBoard Homelab with Debian and Docker
A ZimaCube and ZimaBoard split everyday applications from smart-home services, with Debian, Docker, Pi-hole and a Homepage dashboard.

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.



