What a Pterodactyl-managed Minecraft server taught me about separating player authorization, account authentication, network exposure, and panel access.
A small homelab port shortage reminded me that physical port count, topology, and device capabilities are different problems, and that hardware purchases should come after understanding the path.
What maintaining old and current versions of the same application taught me about treating compatibility as a boundary instead of a temporary inconvenience.
How to make UniFi register VLAN-specific hostnames and distribute a shared DNS search list so clients can reach devices by short name across segmented networks.
The useful part of a homelab is not copying configurations into production. It is practicing the habits that survive a change in platform, scale, and ownership.
Why a game server that worked locally but failed remotely became a better lesson in evidence, network boundaries, and honest troubleshooting than a guessed fix ever could.
Separating storage from application compute forced me to define ownership, permissions, failure boundaries, and recovery instead of treating shared disks as a transparent dependency.
Running Pterodactyl at home made game hosting easier, but the bigger lesson was learning to separate management intent, node control, Docker execution, gameplay, storage, and recovery into distinct failure domains.
Separating application compute from authoritative storage made my homelab easier to rebuild, troubleshoot, and change without pretending a second machine is automatic redundancy.
A healthy container and an empty media library exposed a quieter failure underneath: the path existed, but the filesystem I expected was not mounted there.
Containers gave my homelab a repeatable application model, but the useful part was the discipline around persistence, networking, updates, and recovery.
How inconsistent Docker mounts create failed imports, duplicate copies, broken hardlinks, and misleading permission errors across a media automation stack.
Why I chose UniFi for a home network that needed segmentation, wired multi-AP coverage, useful visibility, and room to experiment without becoming a second full-time job.
A practical architecture and operations handbook for planning a homelab from scratch: workloads, hardware, storage, networking, platforms, security, monitoring, backups, recovery, and the order to build them in.