Homelab Blog
PUBLIC READER FEED

Homelab Architecture & Engineering

Incident post-mortems, architectural blueprints, and platform evolution notes from the scalablepasta infrastructure cluster.

Studio Access
Proxmox NVMe Storage Tiering & Hypervisor Snapshots
Charles Sang • • ID #2

Proxmox NVMe Storage Tiering & Hypervisor Snapshots

High-Performance Thin Pools

Our HP EliteDesk 800 G4 cluster utilizes an NVMe thin-pool (local-lvm) providing crash-consistent hypervisor block snapshots and high throughput for LXC container bind-mounts.

Blog assets uploaded via the publishing studio are written directly to /var/lib/homelab/storage/blog/uploads, which is mapped to high-speed persistent NVMe storage with automated offsite backup synchronization.

Migrating to Sovereign Homelab Infrastructure: Why CT 102 & Rule 17 Matter
Charles Sang • • ID #1

Migrating to Sovereign Homelab Infrastructure: Why CT 102 & Rule 17 Matter

The Imperative of Platform-Tenant Separation

When scaling internal microservices, coupling application logic to infrastructure provisioning scripts leads to configuration drift, permission sprawl, and security debt.

Under Rule 17, tenants consume managed services—such as our central PostgreSQL cluster on CT 102 and local NVMe storage shares—through declarative contracts in config/project.yaml.

Core Invariants Maintained

  1. Zero Plaintext on Disk: Passwords resolve in-memory via 1Password CLI (op read).
  2. Hybrid Access Model: Reader feeds remain public, while the publishing studio is strictly gated by Cloudflare Access Google Workspace SSO.
  3. Closed-Loop Auditing: Every publication triggers automated confirmation to our Dual-Charles notification stream.

This architecture guarantees sovereign data ownership with zero open WAN ports.