stefankoelle/moonweb-site
1
0
Fork 0
mirror of https://github.com/skoelle/moonweb-site.git synced 2026-09-18 01:10:25 +00:00
Code Issues Packages Projects Releases Wiki Activity

Fix comma splices for readability across infra and smarthome articles

Browse Source
This commit is contained in:
stefankoelle
2026-09-11 22:44:11 +02:00
parent a96e9c110e
commit e67a27b9ba
6 changed files with 7 additions and 7 deletions
Download Patch File Download Diff File Expand all files Collapse all files
infra/docker/index.njk
+1 -1
View File
@@ -9,7 +9,7 @@ layout: base.njk
<h1>Docker Container Strategy</h1>
<div class="detail-content">
<p>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 <code>/docker-data/compose/&lt;service&gt;/</code>. 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.</p>
<p>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 <code>/docker-data/compose/&lt;service&gt;/</code>. 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.</p>
<h2>The three Docker hosts</h2>
<ul>
infra/lxc/index.njk
+1 -1
View File
@@ -9,7 +9,7 @@ layout: base.njk
<h1>LXC Container Strategy</h1>
<div class="detail-content">
<p>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.</p>
<p>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.</p>
<h2>Why LXC instead of Docker here</h2>
<ul>
infra/monitoring/index.njk
+2 -2
View File
@@ -11,8 +11,8 @@ layout: base.njk
<p>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.</p>
flat, including the Proxmox host, Docker VM, Synology NAS, and Raspberry
Pi devices, feeds metrics into this central instance.</p>
<h2>What's monitored</h2>
<ul>