Rust architecture and implementation notes
View All Tags
AES-GCM encrypted integration creds in SQLite, .amud-secrets-key on disk. What gets encrypted and what doesn't.
Read article →Storing X-Plex-Token=abc123 in plain text in a yaml file on disk always felt wrong. Storing it in plain text in SQLite felt equally wrong.
Embedded DB for embedded dashboard. WAL mode, single-file backup, no extra container for config storage.
Read article →"Why not Postgres?"
Server in LXC, agent on the hypervisor host. Separation of privileges and why the Unix socket exists.
Read article →"Why not one binary?"
GC pauses, static binaries, Tokio concurrency. Developer brain dump on language choice for AMUD.
Read article →A homelab dashboard is a weird workload. It idles 99% of the time but still needs to poll metrics every few seconds, hold WebSocket connections, encrypt secrets, and never leak memory over months of uptime.
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:
AMUD Dashboard started because my bookmark portal was eating 150MB of RAM and I was tired of YAML. Here's what I built instead.
Read article →My homelab had the usual problem: twenty services, zero good way to open them.
I tried the usual suspects. Heimdall looked nice until I checked htop and saw PHP-FPM doing absolutely nothing useful while holding ~150MB. Homepage was closer to what I wanted — live widgets, clean UI — but I spent an entire Sunday debugging a YAML indent before I admitted I hate editing config files on disk for something as dumb as "add Jellyfin link."
So I did what any reasonable person with too much free time does: I wrote another dashboard.