jhodgkin
960c926dd2
Deployed the new-device feature, checked the live API response instead of assuming the earlier unit test covered it, and found 65/71 devices marked isNew: true. The notification path was correctly bootstrap-safe (verified separately), but the UI's isNew check just tested "first_ever_seen within 24h" with no bootstrap awareness -- and bootstrap timestamps are, correctly, "now", so the whole existing population qualified on day one. Added seen_macs.is_bootstrap, set on the seeding call and excluded from isNew. Migration backfills is_bootstrap=1 for any seen_macs rows that already existed before this column did (the already-deployed CT122 instance) -- verified locally against both a fresh DB and a simulated pre-migration table. 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 + bare-metal
CPU/mem/disk/pressure, historical sparklines, and a LAN device inventory. Local auth always available,
plus an optional "Sign in with Authentik" OIDC button. Live at https://monitor.jerodrigged.com.
Project status, architecture, and how to resume work: see CLAUDE.md.
Playwright e2e tests against the live deployment: see e2e/README.md.
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