Stop Navigating by IP: The Ultimate Homelab Homepage Guide

Welcome to the Asylum: Why Your Homelab Needs a Front Door

Greetings, fellow data-hoarders, rack-mounters, and those of you who find the hum of a 1U server more soothing than a forest stream. They call me Wong Edan, and if you’re reading this, it’s because your browser bookmarks look like a digital landfill. You’ve got Proxmox on one IP, TrueNAS on another, three different Docker instances, a Jellyfin server you use once a month, and an Ollama instance that’s currently hallucinating about electric sheep. You can’t remember the port numbers. Nobody can. Unless you’re a savant or you’ve replaced your blood with thermal paste, you need a homepage.

As Dustin’s legendary guide pointed out back in August 2023, a homelab homepage isn’t just vanity—it’s the “Single Source of Truth.” It’s the difference between a professional-grade private cloud and a pile of e-waste that your spouse wants to throw out. Today, we are going deep. We aren’t just talking about “putting links on a page.” We are talking about integration, real-time monitoring, and the glorious aesthetics of a well-organized dashboard. Buckle up, because we’re going from bare metal to a beautiful GUI.

1. The Foundation: Hardware and Hypervisors

Before we talk about the paint job (the homepage), we need to talk about the garage. According to the latest scrolls from the Homelab community, we are seeing a massive shift in how we build these foundations. Gone are the days when you needed a power-hungry enterprise server that sounds like a Boeing 747 taking off in your closet.

The Rise of the RK3588 (FriendlyElec CM3588)

If you’re looking for efficiency, the FriendlyElec CM3588 (based on the RK3588) has become a darling of the 2024 starter guides. It’s small, it’s powerful, and it doesn’t make your electric meter spin fast enough to create a localized time-warp. When setting up a homepage, having a dedicated, low-power node to host your core infrastructure services—like DNS, Dashboards, and Reverse Proxies—is the “Wong Edan” way. You don’t want your dashboard to go down just because you’re stress-testing a Windows VM on your main rig.

Proxmox 9 and the Virtualization Layer

The community consensus is clear: Proxmox remains the king of the hill. With the transition into Proxmox 9, the integration for local AI and containerization has reached a fever pitch. Your homepage should ideally run in a lightweight Linux Container (LXC) or a dedicated Docker VM. Why? Because when you inevitably break your homepage by messing with a YAML file at 3 AM, you want to be able to restore a snapshot in seconds without affecting your storage arrays.

2. Storage Philosophy: The ZFS “Whole Disk” Strategy

If you’re building a homelab, you’re likely using ZFS. If you aren’t, what are you even doing? Using hardware RAID? It’s 2024, not 2004. Get it together. One of the critical takeaways from recent disk setup best practices is the “Whole Disk” philosophy.

The Strategy: Do not slice your disks into tiny, pathetic partitions. Simply use a single big partition or, better yet, the whole disk for ZFS. This allows all your storage datasets to dynamically share the whole space. When your homepage starts pulling icons, heavy CSS, or localized documentation, you don’t want to be hit with an “Out of Space” error because you were stingy with your /var partition.

“A partitioned disk is a lonely disk. Let the ZFS pool breathe. Let it thrive. Let it consume your data with the hunger of a thousand suns.” – Wong Edan

3. Networking: Fiber Optics to the Shed (Yes, Seriously)

A homepage is useless if you can’t reach it. The “Ultimate Guide to Fiber Optic Home Networking” by apalrd highlights a trend we can’t ignore: extending the lab. Maybe your lab has outgrown the “server closet” and moved to the “server shed.”

If you’re running fiber to an outbuilding, your homepage becomes even more critical. You need to monitor the link state. A good homepage (like the “Homepage” dashboard we’ll discuss later) can use service widgets to tell you if your remote rack is overheating or if the fiber line has been chewed on by a disgruntled squirrel. Reliable internet in the shed isn’t a luxury; it’s a human right for the modern nerd.

4. Choosing Your Weapon: The 7 Best Dashboard Options

Dustin’s guide identified seven different options, but let’s focus on the heavy hitters that the Reddit community (r/homelab and r/Proxmox) has been obsessing over. The standout choice for 2023 and 2024 is the appropriately named “Homepage.”

The “Homepage” Dashboard (The Gold Standard)

This isn’t just a list of links. It’s a modern, insanely fast, highly customizable dashboard that uses YAML for configuration. It supports over 100 service integrations. You want to see your Plex “Now Playing”? It’s there. Want to see your Pi-hole stats? Done. Want to see if your Proxmox nodes are crying for mercy? Easy.

Other Notable Contenders:

• Heimdall: Great for those who fear YAML. It has a nice UI for adding apps, but lacks the deep API integration of “Homepage.”
• Dashy: For the person who wants every feature under the sun and doesn’t mind a bit of configuration bloat.
• Flame: Simple, elegant, lightweight. Perfect for that FriendlyElec CM3588 node.

5. Technical Deep Dive: Setting Up “Homepage”

Since the community has given “Homepage” the “hug of death” on several occasions due to its popularity, let’s look at how to actually deploy it using Docker. This is the heart of the “Ultimate Guide.”

Step 1: The Docker Compose

Create a directory for your configuration and drop this docker-compose.yml file in there. We are mapping the config directory so your hard work survives a container update.


version: "3"
services:
homepage:
image: ghcr.io/gethomepage/homepage:latest
container_name: homepage
ports:
- 3000:3000
volumes:
- /path/to/config:/app/config # Real-world path here, please.
- /var/run/docker.sock:/var/run/docker.sock # Only if you want Docker stats
restart: unless-stopped


Step 2: Configuring Services (services.yaml)

This is where the magic happens. You don’t just put a URL; you put the API key. This allows the homepage to reach out and touch your services, pulling back real-time data.


- My Infrastructure:
- Proxmox:
icon: proxmox.png
href: https://192.168.1.50:8006/
description: The Motherbrain
widget:
type: proxmox
url: https://192.168.1.50:8006
username: root@pam
password: your_secret_password
- Pi-hole:
icon: pi-hole.png
href: http://192.168.1.5/admin
widget:
type: pihole
url: http://192.168.1.5
key: your_api_key_here


6. Leveling Up: Local AI Integration

As per the recent guides on setting up an AI Server Homelab (specifically with Proxmox 9 and Ollama), your homepage should now be the gateway to your local LLMs. If you’ve followed the sequential guides to setting up llama.cpp or Ollama, you can add a service block to your homepage to monitor the status of your AI inference engine.

Why? Because local AI is the new frontier. Running a Llama-3-8B model on your own hardware is the ultimate power move. Seeing that service “Green” on your homepage is the digital equivalent of a lion roaring in the savanna. It lets everyone in your house (or just you and your cat) know that the local intelligence is online and ready to answer stupid questions without sending data to Big Tech.

7. The Human Element: The Home Office Synergy

We often forget that the homelab exists in a physical space. The “Ultimate Home Office Setup Guide” reminds us that a productive workspace is key. Your homepage shouldn’t just be accessible from your desktop; it should be the “kiosk” mode on that secondary monitor or that old iPad you mounted to the wall.

When you walk into your office, your homepage should give you an immediate “Pulse Check” of your digital life. Is the NAS healthy? Is the fiber link to the shed active? Is the AI server ready to compute? If you have to click more than twice to find out, you’ve built a maze, not a dashboard.

Wong Edan’s Verdict

Listen closely, because I’m only going to say this once (per blog post). A homelab without a homepage is just a collection of expensive space heaters. If you are still typing 192.168.x.x:port into your browser like a common peasant, you are doing it wrong.

The Verdict: Install the “Homepage” dashboard. Use the ZFS whole-disk strategy for your underlying storage to avoid headaches. If you have the budget, run fiber to your remote nodes. And for the love of all that is holy, use Proxmox 9 and start experimenting with local AI via Ollama. It is the future, and the future is surprisingly local.

Now, go forth and edit those YAML files. If you break it, just remember: failure is just another way of learning how to fix something you shouldn’t have touched in the first place. Stay crazy, stay labbing.

“In the kingdom of the blind, the man with a functional YAML config is king.” – Wong Edan