My homelab runs almost entirely on Docker, spread across three dedicated Debian VMs instead of installing containers directly on bare metal or on the NAS operating system itself. Each VM is a clean, disposable Docker host that can be snapshotted and backed up as a whole through Proxmox, and every service is defined declaratively as a Docker Compose file living under /docker-data/compose/<service>/. This keeps the setup portable, reproducible, and easy to document, if a host dies, restoring a VM snapshot brings every container definition back with it.
My homelab runs almost entirely on Docker, spread across three dedicated Debian VMs instead of installing containers directly on bare metal or on the NAS operating system itself. Each VM is a clean, disposable Docker host that can be snapshotted and backed up as a whole through Proxmox, and every service is defined declaratively as a Docker Compose file living under /docker-data/compose/<service>/. This keeps the setup portable, reproducible, and easy to document. If a host dies, restoring a VM snapshot brings every container definition back with it.
Alongside the Docker-based setup, I run a small number of Linux Containers (LXC) directly on the main Proxmox host (PVE). An LXC is an OS-level virtualization container, unlike a Docker container, which packages a single application and its dependencies, an LXC behaves like a full lightweight Linux system with its own init process, systemd services and package manager, but without the overhead of a full virtual machine. Proxmox manages LXCs natively as first-class citizens, right next to VMs, with their own snapshotting, backup and resource-limit tooling. I use far fewer LXCs than Docker containers, reserving them for cases where a persistent, OS-like environment or tight integration with Proxmox itself makes more sense than a containerized app.
+Alongside the Docker-based setup, I run a small number of Linux Containers (LXC) directly on the main Proxmox host (PVE). An LXC is an OS-level virtualization container. Unlike a Docker container, which packages a single application and its dependencies, an LXC behaves like a full lightweight Linux system with its own init process, systemd services, and package manager, but without the overhead of a full virtual machine. Proxmox manages LXCs natively as first-class citizens, right next to VMs, with their own snapshotting, backup and resource-limit tooling. I use far fewer LXCs than Docker containers, reserving them for cases where a persistent, OS-like environment or tight integration with Proxmox itself makes more sense than a containerized app.
Prometheus and Grafana form the central monitoring stack for the whole homelab, running as Docker containers on the NAS. Every machine in the -flat, Proxmox host, Docker VM, Synology NAS, and Raspberry Pi devices, -feeds metrics into this central instance.
+flat, including the Proxmox host, Docker VM, Synology NAS, and Raspberry +Pi devices, feeds metrics into this central instance.+20 dB via an ALSA softvol plugin) sits between
shairport-sync and the hardware. The hardware mixer itself is deliberately
left fixed at 100% / 0 dB, and shairport-sync only ever adjusts its own
-internal software volume, this avoids the volume jumps and mixer
+internal software volume. This avoids the volume jumps and mixer
conflicts that show up when multiple layers all try to control loudness.
After moving this Pi to a newer OS release, boot configuration files -moved to a new path, editing the old path silently does nothing, which +moved to a new path. Editing the old path silently does nothing, which is an easy trap when following older notes or tutorials for the same hardware. The lesson: always verify that configuration changes actually take effect, especially after OS upgrades on embedded hardware.
diff --git a/smarthome/tasmota-energy/index.njk b/smarthome/tasmota-energy/index.njk index 576249c..b14b42e 100644 --- a/smarthome/tasmota-energy/index.njk +++ b/smarthome/tasmota-energy/index.njk @@ -27,7 +27,7 @@ and LED matrix displays.Several rooms use multi-outlet smart power strips (each socket -individually switchable and metered) rather than single smart plugs, this +individually switchable and metered) rather than single smart plugs. This keeps things like "washing machine + dryer" or "office desk cluster" on one strip while still tracking each socket's consumption separately.