Unify Proxmox host as Beelink S12 Pro; remove false monitoring-backup open item

infra/index.njk

@@ -41,7 +41,7 @@ sections:
 
 <section class="about-expanded">
   <h2>The setup at a glance</h2>
-  <p>The infrastructure runs on three main machines: a Proxmox VE host (Intel NUC, 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.</p>
+  <p>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.</p>
   <p>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.</p>
 
   <h2>Why Proxmox</h2>

infra/monitoring/index.njk

@@ -52,7 +52,6 @@ temperature thresholds) are planned but not yet implemented.</p>
 <li>Alerting rules are not yet configured for most services.</li>
 <li>The secondary (test) Proxmox host isn't monitored yet, it's usually powered off.</li>
 <li>Retention policy for Prometheus data hasn't been tuned.</li>
-<li>Monitoring data itself isn't currently backed up.</li>
 </ul>
 
 </div>

infra/proxmox/index.njk

@@ -13,7 +13,7 @@ layout: base.njk
 
 <h2>Hardware</h2>
 <ul>
-<li><strong>PVE (main server)</strong>, a Beelink Mini-PC, running as the primary Proxmox host. It has a 500GB SSD for VM and container storage, and connects to the network via the server-room Zyxel switch.</li>
+<li><strong>PVE (main server)</strong>, a Beelink S12 Pro, running as the primary Proxmox host. It has a 500GB SSD for VM and container storage, and connects to the network via the server-room Zyxel switch.</li>
 <li><strong>pve2 (test server)</strong>, a second Proxmox host, physically located in the study and connected via the OpenWRT-side Zyxel switch. It's dedicated purely to testing and development, running the third <a href="/infra/docker/">Docker host VM (docker-host-pve2)</a> plus experimental setups without risking the production environment.</li>
 <li><strong>Backups</strong>, nightly VM backups from PVE run at 00:30 to an NFS share on the Synology (<code>nas:/volume1/backup</code>), with retention of the last 3 daily, 3 monthly and 1 yearly backup.</li>
 </ul>