From 96f9f0b6294b58d288e9eeacf26b8de563f5661b Mon Sep 17 00:00:00 2001 From: Stefan Koelle Date: Fri, 11 Sep 2026 22:31:58 +0200 Subject: [PATCH] Fix Beelink S12 Pro RAM to 32GB --- infra/index.njk | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/infra/index.njk b/infra/index.njk index 97781cc..043f35c 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, 64GB 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 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 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 3-2-1 strategy: local snapshots, NAS copies, offsite sync to a Raspberry Pi in a different room, and cloud archive for worst-case scenarios.

Why Proxmox