Homelab

The lab exists to support live work: sites, routing, monitoring, storage, and the boring recovery paths that keep those surfaces usable.

Node map

physical nodes

nuc1     dev tooling / available
nuc2     always-on core
nuc3     dns backup
nuc4     media
m710q3   client hosting
m93p     monitoring / intelligence
optiplex observability / staging / repurpose
nas      storage

m710q2   offline
m710q1   offline

Hardware / status surface

nuc1 available tracked

nuc2 core tracked

nuc3 dns backup tracked

nuc4 media tracked

m710q3 client hosting tracked

m93p monitoring tracked

optiplex staging tracked

nas storage tracked

m710q2 parked down

m710q1 parked down

This area should eventually become a live Proxmox-style view with CPU and memory overlays. For now it is the hardware/status surface instead of a fake photo prompt.

Services

Public-facing services

routes and surfaces

ericminish.com
  personal site

nmwelldrilling.com
  disclosed sample / reference implementation

thefrostlineco.com
  provider-facing business site

Internal services

service layer

adguard primary
adguard backup
caddy edge
nginx sites
uptime kuma
ntfy
cups
scraper_miwine

Why It Matters

Separation helps

The useful part of the lab is not the node count. It is having clear separation between boxes, services, and public surfaces so changes are easier to reason about and failures are easier to isolate.

Uptime Kuma is the monitoring piece I most want to surface here. A better next version of this page would turn the hardware/status block above into a real status view instead of a static sketch.

Email is the best way to reach me — [email protected].