From 1828188fd7c758efe95f30712d2300c2d97a3aa6 Mon Sep 17 00:00:00 2001 From: Stefan Koelle Date: Fri, 11 Sep 2026 23:08:31 +0200 Subject: [PATCH] Fix infra machine count: two Beelink Proxmox hosts + Synology, VM moved out of device list --- infra/index.njk | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/infra/index.njk b/infra/index.njk index 9839128..d1ac3be 100644 --- a/infra/index.njk +++ b/infra/index.njk @@ -41,7 +41,7 @@ sections:

The setup at a glance

-

The infrastructure runs on three main machines: a Proxmox VE host (Beelink S12 Pro, 32GB RAM) as the primary compute node, a Synology DS918+ NAS for storage and Docker services, and a Xubuntu VM on Proxmox for development. An OpenWrt router handles multi-WAN failover with WiFi and Powerline backhaul, and four Zyxel GS1200-8HP managed switches distribute the network across the flat.

+

The infrastructure runs on three physical machines: a Beelink S12 Pro running Proxmox as the primary host, a second Beelink running Proxmox as a test host, and a Synology DS918+ NAS for storage and Docker services. Development runs in a Xubuntu VM on the Proxmox hosts. An OpenWrt router handles multi-WAN failover with WiFi and Powerline backhaul, and four Zyxel GS1200-8HP managed switches distribute the network across the flat.

The whole stack is monitored via Prometheus and Grafana, with node exporters on every machine, cAdvisor for container metrics, and SNMP exporters for network hardware. Backups follow a layered strategy: local snapshots, NAS copies, offsite sync to a Raspberry Pi in a different room, and cloud archive for worst-case scenarios.

Why Proxmox