jhodgkin
04282232cc
Runs as a host-level systemd timer on CT122 (scripts/discover-devices.sh) rather than inside the api container, since real ARP entries live in the host's network namespace, not Docker's bridge network. See docs/device-discovery.md for the full writeup, including why literal passive-only ARP reading was dropped (near-empty result in practice). API reads the resulting JSON file each poll cycle, cross-references config/hosts.yaml's knownDevices list by IP, and serves /api/devices. Dashboard gets a new "Network Devices" table. Closes #9. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Homelab Monitor
A single dashboard for the health of everything in the homelab (documented in
jhodgkin/homelab): Proxmox host + LXC
CPU/mem/disk/pressure, and — as the backlog fills in — SSH-monitored bare-metal boxes, a LAN
device inventory, and Zabbix alerts. One login instead of N.
Project status, architecture, and how to resume work: see CLAUDE.md.
Roadmap: Gitea issues, milestone v1-dashboard.
Local development
# terminal 1
cd apps/api && npm install && cp ../../.env.example ../../.env # fill in .env first
npm run dev
# terminal 2
cd apps/web && npm install && npm run dev
Web dev server proxies /api to localhost:3000 (see apps/web/vite.config.ts).
Production deploy
Runs as Docker Compose on CT122 (homelab-monitor, 192.168.1.103):
ssh homelab-monitor
cd /opt/homelab-monitor
git pull
docker compose up -d --build