Build a Home Lab Dashboard with Homepage

Who This Is For

Beginner.

Think of it like a universal remote instead of walking to every room to check the thermostat, the lights, and whether the door's locked.

What You'll Build

A polished dashboard with service groups, live health data, and no exposed secrets.

Prerequisites

Docker host
A handful of running services to link

Deploy Homepage

$services:
$ homepage:
$ image: ghcr.io/gethomepage/homepage:latest
$ ports: ["3000:3000"]
$ volumes:
$ - ./config:/app/config

Basic YAML Configuration

Homepage is configured entirely through YAML files under config/, services, widgets, bookmarks, and settings each get their own file.

Organize Categories

Core infrastructure
Storage
Security
Media
Monitoring
Development

Add Widgets

Uptime Kuma status
AdGuard Home stats
Proxmox resource usage
Docker container list
Grafana snapshot
Jellyfin now-playing

Docker Label Discovery

Homepage can auto-discover services from Docker labels instead of hand-editing YAML for every container, worth enabling once you have more than a handful of services.

Keep Sensitive Services Off an Unauthenticated Page

Put the dashboard itself behind a VPN or reverse-proxy authentication if any linked widget can expose personal data.

Security & Backup Notes

Widget API keys need real permissions to pull live data, store them in Homepage's secrets file, not directly in the YAML you might screenshot or commit

Troubleshooting

Widget API key permissions, most widgets need a specific scoped API key, not your main admin credential
Broken service links, usually a stale IP after a service moved; fix at the source with local DNS instead
Docker discovery not working, confirm the Homepage container has access to the Docker socket
Dashboard exposed without authentication, add a reverse-proxy auth layer or keep it VPN/LAN-only

Lab Finish Line

A polished dashboard with service groups, health data, and no exposed secrets.