<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Proxmox on Wilhelm Maritz</title><link>https://wjmaritz.dev/tags/proxmox/</link><description>Recent content in Proxmox on Wilhelm Maritz</description><generator>Hugo -- gohugo.io</generator><language>en</language><lastBuildDate>Sun, 18 Oct 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://wjmaritz.dev/tags/proxmox/index.xml" rel="self" type="application/rss+xml"/><item><title>My NAS was doing a server's job, so I bought it a server</title><link>https://wjmaritz.dev/posts/nas-bought-a-server/</link><pubDate>Sun, 18 Oct 2026 00:00:00 +0000</pubDate><guid>https://wjmaritz.dev/posts/nas-bought-a-server/</guid><description>&lt;p&gt;My ZimaBoard started as a NAS. By October it was also running Immich and Paperless, Uptime Kuma, Grafana and Prometheus, a Homepage dashboard, two small metrics bridges, and a container full of AI coding agents. All of that on 7.5 GiB of RAM, with &lt;a href="https://wjmaritz.dev/posts/grafana-memory-limit/"&gt;Grafana alone needing a whole gigabyte&lt;/a&gt; of it.&lt;/p&gt;
&lt;p&gt;The board was coping on average. What worried me was the agents&amp;rsquo; container. It wasn&amp;rsquo;t the steady use; it was what happens when an agent runs &lt;code&gt;npm install&lt;/code&gt; or a test suite and that spike lands on the same memory Immich and Paperless are using. So on 16 October a GMKtec K10 went onto the desk beside it, and the board went back to being mostly a NAS.&lt;/p&gt;</description></item></channel></rss>