Laurent Brand home
← Portfolio homelab
Browse homelab topics

Homelab / Technical documentation

Two hosts. Explicit runtime boundaries.

The confirmed deployment separates the main Docker workload from home automation, DNS and monitoring.

Jump to a section

Deployment, confirmed 8 November

HP · Primary Proxmox host

Debian VM

Docker

Main application services: media, document processing and management tools.

Tailscale LXC

Remote-access role

Windows 11 VM

Separate Windows workload

ASUS · Second Proxmox host

Home Assistant OS VM

Dedicated home-automation guest

Debian VM

Docker
  • Pi-hole · DNS role
  • Uptime Kuma · monitoring
Deployment diagram · User-confirmed, S19. Nested boxes mean containment. No line implies shared storage, network isolation, replication or failover.

Uptime Kuma monitors the primary host and its services. This is a monitoring relationship from the second host, not an automatic recovery mechanism.

Evidence: S15 · S19.

Why these boundaries matter

Moving the application stack into a Debian Docker VM gave the migration a distinct Linux runtime and a place for persistent appdata. The confirmed second-host layout puts DNS, monitoring and Home Assistant outside that primary VM. That reduces their dependence on the main guest; it does not prove independence from power, routing or shared physical storage.

Home Assistant OS is a VM on the ASUS. It should not be drawn as another container in the primary Docker stack. Pi-hole and Kuma are separate containers inside the ASUS Debian VM, while Tailscale remains an LXC on the HP.

Evidence: S04 · S19.

Hardware facts with dates

Scroll within the table to see all columns.

Hardware evidence, not a current capacity inventory
ComponentEvidence
HP Slim Desktop S01-pF0xxxRecovered hardware identification; Intel Core i5-9400 and UHD 630. Earlier EliteDesk wording is superseded. S01.
WD Blue SN570Recovered identification: 250 GB NVMe model. S01.
ASUS ROG laptopUser-described July inventory: i7-6700HQ, 16 GB RAM, GTX 960M; later confirmed as the second Proxmox host. S01, S19.
Debian Docker VMNovember transcript reports Debian 13 and a 6.12-series guest kernel. A guest kernel is not a Proxmox release. S05.

The record establishes two operating hosts. It does not establish cluster membership, quorum, HA or a tested failover path. Current RAM and PVE release numbers are intentionally omitted because older records conflict.

Evidence: S01 · S05 · S19.

Read-only inventory checks

Illustrative · read-only · run separately on each authorized Proxmox host
pveversion
qm list
pct list
pvecm status

Use the output to distinguish host release, guest identity and cluster membership. A standalone node may not have cluster status. Keep addresses, guest names and configuration exports private; publish only the fields needed to explain the deployment.