Why AMUD Dashboard Is Two Binaries Instead of One Blob
Server in LXC, agent on the hypervisor host. Separation of privileges and why the Unix socket exists.
Read article →"Why not one binary?"
5 publicaciones etiquetados con "Proxmox"
Proxmox VE installs, LXC, and API integration
Ver Todas las Etiquetas
Why Your App Cards Are Stuck on CHECKING...
CPU bars work but LXC badges don't? It's almost always the Proxmox API token. Here's how to read agent logs and fix it.
Read article →Top bar shows live CPU. App cards say CHECKING... forever.
Green and Red LXC Badges (Plus Start/Stop From the Dashboard)
Link an app card to a CTID, get live RUNNING/STOPPED status, and optionally power-cycle containers without opening Proxmox.
Read article →A link list tells you where Jellyfin should be. It doesn't tell you Jellyfin is stopped because you updated the LXC last night and forgot to bring it back up.
Real-Time Homelab Telemetry Without Spawning Shell Scripts
Most dashboards shell out to pvesh or docker stats every few seconds. AMUD Dashboard reads /proc and talks to APIs natively in Rust.
Read article →Here's a pattern I've seen in a lot of homelab monitoring glue:
Install AMUD Dashboard on Proxmox in One Command (No Docker)
One curl on your Proxmox host provisions an LXC, installs the agent on the hypervisor, and gives you a working dashboard on port 8000.
Read article →Docker is fine. I use it. But wrapping a dashboard — a thing that mostly displays links and polls metrics — inside another network stack on a Proxmox box always felt like wearing two coats indoors.