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.
AMUD Dashboard encrypts integration secrets at rest with AES-GCM. Plex, Jellyfin, Proxmox API tokens, Home Assistant tokens — encrypted blob in the database, not readable if someone copies amud.db without the key.
.amud-secrets-key on the host. Derived key material for encryption/decryption at runtime.
Back it up with your database. Restore DB without key = your tokens are toast. You'll re-enter them in settings. Annoying but not catastrophic.
\nApp URLs, card names, layout stuff — none of that's secret. Your Jellyfin URL being http://10.0.0.5:8096 isn't the sensitive part. The API key is.
Password hashes use Argon2id separately. Different layer. Same philosophy: don't store usable secrets in recoverable form.
\nThis stops \"someone copied my backup drive\" from leaking your Proxmox token. It doesn't stop someone with root on your running server — they own the box anyway.
\nHomelab threat model. Not banking.
\nFull security writeup: /docs/security
\nRotate tokens in integrations settings if you think the DB leaked. Same as any other dashboard.
", "url": "https://boubli.github.io/AMUD-Dashboard/blog/encrypted-secrets-at-rest", "title": "Where Your Plex Token Actually Lives in AMUD Dashboard", "summary": "AES-GCM encrypted integration creds in SQLite, .amud-secrets-key on disk. What gets encrypted and what doesn't.", "date_modified": "2026-02-25T00:00:00.000Z", "author": { "name": "Youssef Boubli", "url": "https://github.com/boubli" }, "tags": [ "Security", "Rust" ] }, { "id": "https://boubli.github.io/AMUD-Dashboard/blog/sqlite-wal-not-postgres", "content_html": "\"Why not Postgres?\"
\nBecause then I'd need to run Postgres.
\nAMUD Dashboard is a dashboard. Config storage is a few hundred KB of apps, settings, and encrypted tokens. Running a whole separate database server for that is like buying a warehouse to store a shoebox.
\nWrite-Ahead Logging lets readers (the web UI loading settings) coexist with writers (you saving a new app card) without the lock contention that makes people hate SQLite in web apps from 2010.
\nFor a single-tenant homelab dashboard with one admin clicking settings occasionally? Perfect fit.
\namud.db sits next to the binarycp amud.db backup.dbsqlite3 amud.db when debuggingI've done all of these at 1am. Postgres would add connection strings, another service to monitor, another thing to backup separately.
\nMulti-tenant SaaS. Hundreds of concurrent writers. Horizontal scaling. AMUD Dashboard is explicitly none of those — see roadmap \"won't do SaaS.\"
\nHomelab tool. Homelab database. Match the complexity to the problem.
\n", "url": "https://boubli.github.io/AMUD-Dashboard/blog/sqlite-wal-not-postgres", "title": "Why AMUD Dashboard Uses SQLite Instead of Postgres (Yes, Really)", "summary": "Embedded DB for embedded dashboard. WAL mode, single-file backup, no extra container for config storage.", "date_modified": "2026-02-23T00:00:00.000Z", "author": { "name": "Youssef Boubli", "url": "https://github.com/boubli" }, "tags": [ "Rust", "Homelab" ] }, { "id": "https://boubli.github.io/AMUD-Dashboard/blog/migrated-from-homepage", "content_html": "I ran Homepage for a year. Liked it. Still recommend it for the right person.
\nSwitching to AMUD Dashboard wasn't \"Homepage bad, AMUD Dashboard good.\" It was \"I'm tired of this specific workflow.\"
\nservices.yaml in a repo.amud.db instead of yaml + env + secrets scattered around.You like GitOps. You generate configs from Ansible. You want fifty community widgets. YAML doesn't make you twitch.
\nProxmox primary. YAML fatigue. Want live LXC status without shell scripts. Okay with \"config in a database\" as the trade.
\nMigration tip: screenshot your Homepage layout, recreate cards in AMUD Dashboard while watching TV. Took me about forty minutes for ~25 services. Your mileage varies.
\ncurl -sSL https://raw.githubusercontent.com/boubli/AMUD-Dashboard/main/setup-amud.sh | bash
\"Why not one binary?\"
\nBecause on Proxmox the dashboard server lives in an unprivileged LXC and the thing that talks to /proc, the Docker socket, and the PVE API on port 8006 needs to live on the host.
Different trust boundaries. Different privilege levels.
\namud user in the LXCThey talk over /opt/amud/run/amud.sock. Bind-mounted into the LXC on Proxmox installs. Shared Docker volume in container deployments.
The socket isn't world-writable chaos. Agent proves it knows AMUD_AGENT_SECRET before the server accepts telemetry. Stops random local processes from feeding fake metrics.
On single-box Docker or bare-metal where server and agent share a host, they're still separate processes for isolation. Server crash doesn't take down polling. Agent restart doesn't drop active web sessions.
\nMight be over-engineered for a homelab. I'd rather over-engineer the security boundary than under-engineer it.
\n", "url": "https://boubli.github.io/AMUD-Dashboard/blog/why-two-binaries", "title": "Why AMUD Dashboard Is Two Binaries Instead of One Blob", "summary": "Server in LXC, agent on the hypervisor host. Separation of privileges and why the Unix socket exists.", "date_modified": "2026-02-19T00:00:00.000Z", "author": { "name": "Youssef Boubli", "url": "https://github.com/boubli" }, "tags": [ "Rust", "Proxmox", "Homelab" ] }, { "id": "https://boubli.github.io/AMUD-Dashboard/blog/contribute-to-amud", "content_html": "AMUD Dashboard isn't a startup. It's a homelab tool I built because I wanted it. But it gets better when other people break it in ways I didn't imagine.
\ngithub.com/boubli/AMUD-Dashboard
\nStars help GitHub discovery and lists like awesome-selfhosted. Sounds shallow. Matters anyway.
\nProxmox version, RAM numbers, screenshot of your dashboard. GitHub Discussions is the place. \"Works on my weird ARM NAS\" posts are gold.
\njournalctl -u amud-agent -n 50 outputVague \"doesn't work\" issues sit longer. Fair warning.
\n| Area | Stack |
|---|---|
| amud-server | Rust, Axum |
| amud-agent | Rust, Tokio |
| UI | HTML, Alpine.js, CSS |
| Docs | Docusaurus, Markdown |
| Themes | CSS variables |
Roadmap: /docs/roadmap — ARM64 CI, webhooks, multi-node agents on the list.
\nCSS file + preview screenshot → PR to docs/static/themes/ → shows up in /themes.
That's a contribution normies can do without touching Rust. Please do.
\nThanks for reading this series. Go break something and file an issue.
", "url": "https://boubli.github.io/AMUD-Dashboard/blog/contribute-to-amud", "title": "AMUD Dashboard Is Open Source — Here's How to Actually Help", "summary": "Stars, issues, PRs, themes, docs. Homelab projects grow from real users reporting real weird setups.", "date_modified": "2026-02-17T00:00:00.000Z", "author": { "name": "Youssef Boubli", "url": "https://github.com/boubli" }, "tags": [ "Homelab", "Self-Hosted" ] }, { "id": "https://boubli.github.io/AMUD-Dashboard/blog/why-rust-for-homelab-daemon", "content_html": "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.
\nThat's systems programming territory. Not \"spin up Express and call it a day\" territory.
\nI've run plenty of Node homelab tools. V8 heap sitting at 80–150MB for a bookmark page hurts when that box also runs Jellyfin and Sonarr. GC pauses during telemetry polling are rare but annoying when you're staring at a graph that stutters.
\nGo would've been fine honestly. I picked Rust because I wanted memory safety without a GC, static binaries with embedded assets (include_str! for UI templates), and Tokio's async model for concurrent integration polls.
Compile once, drop binary on host, run. No runtime install step.
\nRust compile times are slow. Contributor pool is smaller than JS. I occasionally fight the borrow checker at 2am.
\nFor a long-running daemon on a 256MB LXC though? I'd make the same call again.
\nArchitecture: /docs/ARCHITECTURE
\nWant to hack on it: github.com/boubli/AMUD-Dashboard
", "url": "https://boubli.github.io/AMUD-Dashboard/blog/why-rust-for-homelab-daemon", "title": "Why I Picked Rust for a Dashboard That Sits Idle All Day", "summary": "GC pauses, static binaries, Tokio concurrency. Developer brain dump on language choice for AMUD.", "date_modified": "2026-02-15T00:00:00.000Z", "author": { "name": "Youssef Boubli", "url": "https://github.com/boubli" }, "tags": [ "Rust", "Homelab" ] }, { "id": "https://boubli.github.io/AMUD-Dashboard/blog/portainer-deploy", "content_html": "I live in SSH. Some of you live in Portainer. Both are valid.
\nAMUD Dashboard deploys as a stack: amud_app + amud_agent + amud_run volume.
amudAMUD_AGENT_SECRET to something long and randomAgent needs /var/run/docker.sock:ro and AMUD_DOCKER=1.
http://your-host:8000 → login → change password → add cards in UI.
Bind ./data to a host path you snapshot. That's your backup.
Portainer-specific notes: /docs/installation/portainer
\nDocker path uses a bit more RAM than native Proxmox LXC. Trade-off for convenience.
", "url": "https://boubli.github.io/AMUD-Dashboard/blog/portainer-deploy", "title": "Deploying AMUD Dashboard Through Portainer (For Clickers Not SSHers)", "summary": "Stack template, matching AMUD_AGENT_SECRET, Docker socket mount. GUI homelab crowd deserves dashboards too.", "date_modified": "2026-02-13T00:00:00.000Z", "author": { "name": "Youssef Boubli", "url": "https://github.com/boubli" }, "tags": [ "Docker", "Homelab" ] }, { "id": "https://boubli.github.io/AMUD-Dashboard/blog/wall-mounted-dashboard", "content_html": "I've got an old iPad on a desk mount running AMUD Dashboard in guest mode. Shows CPU, which lights are on, if Plex is streaming, whether the *arr stack is actually running. Wife approves because it doesn't look like a terminal.
\nSettings → Appearance
\nSkip the admin controls on a shared display. Guest account.
\n--kioskPoint at your HTTPS URL (see the reverse proxy post). WebSockets need to work or the graphs lie.
\nThat's it. Old hardware, new purpose, zero YAML.
", "url": "https://boubli.github.io/AMUD-Dashboard/blog/wall-mounted-dashboard", "title": "Turning an Old Tablet Into a Homelab Status Board", "summary": "Grid density, guest mode, theme gallery wallpapers, kiosk browser tips. AMUD Dashboard was basically made for wall mounts.", "date_modified": "2026-02-11T00:00:00.000Z", "author": { "name": "Youssef Boubli", "url": "https://github.com/boubli" }, "tags": [ "Homelab", "Themes" ] }, { "id": "https://boubli.github.io/AMUD-Dashboard/blog/admin-vs-guest", "content_html": "Put a dashboard on a kitchen wall tablet. Someone will eventually tap the wrong button.
\nAMUD Dashboard has Admin and Guest roles. Guests get links. Admins get the keys to the kingdom.
\nAdmins keep full power controls on linked LXCs. Guests just see whether stuff is running without the big red stop button.
\n", "url": "https://boubli.github.io/AMUD-Dashboard/blog/admin-vs-guest", "title": "Guest Mode So Your Family Doesn't Stop the Plex Container", "summary": "Admin sees power controls. Guest sees links and optional telemetry. Kitchen tablet stays safe.", "date_modified": "2026-02-09T00:00:00.000Z", "author": { "name": "Youssef Boubli", "url": "https://github.com/boubli" }, "tags": [ "Homelab", "Security" ] }, { "id": "https://boubli.github.io/AMUD-Dashboard/blog/fix-checking-badge", "content_html": "Top bar shows live CPU. App cards say CHECKING... forever.
\nWelcome to the most common AMUD Dashboard support question. Good news: it's usually one of like four things.
\njournalctl -u amud-agent --no-pager -n 20
Look for [LXC] lines:
| Log | Meaning |
|---|---|
PVE_API_TOKEN not set | Token missing from systemd env |
Successfully fetched 0 containers | Privilege Separation still on |
HTTP 401 | Wrong token secret |
HTTP 500/595 | Bad node hostname in config |
nano /etc/systemd/system/amud-agent.service
Under [Service]:
Environment=\"PVE_API_TOKEN=PVEAPIToken=amud@pve!amud-token=YOUR-SECRET\"
systemctl daemon-reload && systemctl restart amud-agent
Also paste the same token in the UI under Settings → Proxmox VE. Both places. Yes, redundant. Yes, necessary.
\nWhen creating the API token in Proxmox, uncheck Privilege Separation. I cannot stress this enough. Spent two hours on this once. Not proud.
\npct list
Make sure the app card ID matches reality.
\nFull troubleshooting bible: /docs/troubleshooting
", "url": "https://boubli.github.io/AMUD-Dashboard/blog/fix-checking-badge", "title": "Why Your App Cards Are Stuck on CHECKING...", "summary": "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.", "date_modified": "2026-02-07T00:00:00.000Z", "author": { "name": "Youssef Boubli", "url": "https://github.com/boubli" }, "tags": [ "Proxmox", "Homelab" ] }, { "id": "https://boubli.github.io/AMUD-Dashboard/blog/backup-amud-db", "content_html": "I've seen people maintain elaborate backup scripts for YAML dashboards — git repos, env files, secret sidecars, three different paths.
\nAMUD Dashboard backup:
\ncp /opt/amud/data/amud.db ~/backups/amud-$(date +%F).db
Done. Apps, tabs, settings, users, encrypted creds (encrypted blob in DB).
\namud-serveramud.dbamud-serverYour dashboard is exactly as it was. I've used this to clone a test setup to prod. Worked first try.
\nIntegrations use .amud-secrets-key for AES-GCM. Backup it with the database. Restore DB without key = encrypted tokens become useless noise.
0 3 * * * cp /opt/amud/data/amud.db /mnt/nas/backups/amud-$(date +\\%F).db
Keep a week of dailies. Homelab disasters always happen on the day you skipped backups.
\nMore: /docs/troubleshooting
", "url": "https://boubli.github.io/AMUD-Dashboard/blog/backup-amud-db", "title": "Back Up Your Entire Dashboard in One File", "summary": "amud.db is your whole config. Copy it. Don't forget .amud-secrets-key if you use encrypted integrations.", "date_modified": "2026-02-05T00:00:00.000Z", "author": { "name": "Youssef Boubli", "url": "https://github.com/boubli" }, "tags": [ "Homelab", "Self-Hosted" ] }, { "id": "https://boubli.github.io/AMUD-Dashboard/blog/bare-metal-linux-install", "content_html": "Sometimes you have a spare NUC or mini PC that does one job: show the dashboard on a wall and nothing else.
\nDocker on that box is overhead you don't need.
\n/opt/amud/run → Unix socket
/opt/amud/data → amud.db
/opt/amud/ui → templates
sudo groupadd --system amud
sudo useradd --system -g amud -s /sbin/nologin amud
sudo mkdir -p /opt/amud/run /opt/amud/data /opt/amud/ui
sudo chown -R amud:amud /opt/amud
Server runs as amud. Agent typically needs more privileges for host metrics — see the full guide for the permission model.
Grab latest from GitHub Releases. Drop amud-server and amud-agent in /usr/local/bin/, set up systemd units, go.
Works on Debian, Ubuntu, Fedora, Arch — anything with systemd.
\nFull walkthrough: /docs/installation/linux
\nWhen I'd pick this over Proxmox LXC: dedicated dashboard hardware, no hypervisor, absolute minimum RAM.
", "url": "https://boubli.github.io/AMUD-Dashboard/blog/bare-metal-linux-install", "title": "Running AMUD Dashboard on Bare Metal (No Docker, No LXC)", "summary": "Dedicated amud system user, /opt/amud layout, systemd units. Lowest overhead if you have a spare NUC.", "date_modified": "2026-02-03T00:00:00.000Z", "author": { "name": "Youssef Boubli", "url": "https://github.com/boubli" }, "tags": [ "Homelab", "Self-Hosted" ] }, { "id": "https://boubli.github.io/AMUD-Dashboard/blog/amud-vs-heimdall-homepage-homarr", "content_html": "I built AMUD. I'm biased. Here's the honest comparison anyway.
\n| AMUD | Heimdall | Homepage | Homarr | |
|---|---|---|---|---|
| Runtime | Rust binary | PHP/Laravel | Node/React | Next.js |
| Config | SQLite + UI | DB + UI | YAML | UI + files |
| Idle RAM | ~26–35MB (PVE native) | ~150MB | varies | 200MB+ |
| Proxmox LXC control | native | no | widgets | limited |
| YAML required | never | no | yes | partial |
You want simple bookmarks and PHP on your server doesn't bother you. No live telemetry needed.
\nYou live in Git, love YAML, want the widget ecosystem. You're good at debugging indent errors. Respect.
\nYou want the polished drag-drop UI and don't care about RAM. *arr integration out of the box matters to you.
\nSaaS. YAML-first config. Node/PHP dependency. It's a homelab tool. Stays that way.
\ncurl -sSL https://raw.githubusercontent.com/boubli/AMUD-Dashboard/main/setup-amud.sh | bash
Deployed AMUD Dashboard behind Nginx, opened the page, everything looked fine except the CPU bar was stuck at 0% like the server was dead. Server wasn't dead. Nginx just ate the WebSocket upgrade.
\nAMUD Dashboard streams telemetry over WebSockets. Your reverse proxy must forward upgrade headers or you get a pretty but useless dashboard.
\nlocation / {
proxy_pass http://127.0.0.1:8000;
proxy_set_header Host $host;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header X-Forwarded-Proto $scheme;
proxy_http_version 1.1;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection \"upgrade\";
}
Once you're on HTTPS:
\nAMUD_SECURE_COOKIES=1
Restart the server. Forget this and you'll chase phantom login bugs.
\namud.homelab.local {
reverse_proxy localhost:8000
}
Usually just works. Caddy's the easy mode.
\nFull configs: /docs/installation/reverse-proxy
\nAfter setup: login works, graphs move, LXC badges update. If not, browser console first. Always browser console first.
", "url": "https://boubli.github.io/AMUD-Dashboard/blog/reverse-proxy-websockets", "title": "Putting AMUD Dashboard Behind Nginx Without Breaking Live Metrics", "summary": "If your CPU graphs freeze at 0%, your reverse proxy probably isn't forwarding WebSocket upgrades. Fix inside.", "date_modified": "2026-01-30T00:00:00.000Z", "author": { "name": "Youssef Boubli", "url": "https://github.com/boubli" }, "tags": [ "Homelab", "Security" ] }, { "id": "https://boubli.github.io/AMUD-Dashboard/blog/securing-homelab-dashboard", "content_html": "Your dashboard is a map to your entire homelab. Treat it like one.
\nArgon2id hashes in SQLite. Not SHA-256 alone, not md5 (please). Older installs with legacy SHA-256 get transparently re-hashed on next login.
\n32-byte random tokens, 24h lifetime, HttpOnly, SameSite=Strict. Behind HTTPS set AMUD_SECURE_COOKIES=1 or you're leaving cookies exposed on misconfigured proxies.
5 failed logins per username in 5 minutes. Enough to stop dumb scripts, not enough to lock you out forever if you typo once.
\nPlex tokens, Jellyfin keys, Proxmox API tokens, HA tokens — AES-GCM encrypted at rest with a host keyfile (.amud-secrets-key). Backup that file with your database or restores get awkward.
State-changing requests need CSRF tokens. CSP with per-request nonces on scripts. Boring security stuff that matters when your dashboard is internet-facing behind a reverse proxy.
\nadmin / password (seriously)AMUD_SECURE_COOKIES=1amud.db and .amud-secrets-keyFull doc: /docs/security
", "url": "https://boubli.github.io/AMUD-Dashboard/blog/securing-homelab-dashboard", "title": "Securing a Dashboard That Knows Where Everything Lives", "summary": "Argon2id passwords, encrypted integration secrets, CSRF, rate limiting — what AMUD Dashboard actually ships with.", "date_modified": "2026-01-28T00:00:00.000Z", "author": { "name": "Youssef Boubli", "url": "https://github.com/boubli" }, "tags": [ "Security", "Self-Hosted" ] }, { "id": "https://boubli.github.io/AMUD-Dashboard/blog/twelve-free-themes", "content_html": "The default AMUD Dashboard look is orange glass. I like it. My partner said it looked like a Cheetos-themed spaceship cockpit. Fair.
\nSo I built a theme gallery with twelve ready-made CSS themes and actual dashboard preview screenshots so you can pick before you paste.
\nDracula, Nord, Catppuccin Mocha, Tokyo Night, Gruvbox Dark, Cyberpunk Neon, Solarized Dark, Rose Pine, Everforest, Monokai, One Dark, Sunset Warm.
\nInstant. No restart. No import-from-URL (that feature got cut on purpose — copy-paste is safer and works offline).
\nEach theme has a bundled 2K wallpaper. Copy wallpaper URL → paste into background image setting. Makes wall tablets look intentional instead of \"sysadmin panel accidentally left on.\"
\nBroke the layout with bad CSS? Been there. Recovery guide: /docs/troubleshooting
\nWant to roll your own? CSS variable reference: /docs/themes
", "url": "https://boubli.github.io/AMUD-Dashboard/blog/twelve-free-themes", "title": "12 Free Themes Because Orange Glass Isn't for Everyone", "summary": "Copy-paste CSS from the theme gallery. Dracula, Nord, Catppuccin, Cyberpunk Neon, and eight more with preview screenshots.", "date_modified": "2026-01-26T00:00:00.000Z", "author": { "name": "Youssef Boubli", "url": "https://github.com/boubli" }, "tags": [ "Themes", "Homelab" ] }, { "id": "https://boubli.github.io/AMUD-Dashboard/blog/home-assistant-dashboard-card", "content_html": "I had a Home Assistant card that was literally just a URL. Useful, but my wall tablet deserved better.
\nAMUD Dashboard can show on that card:
\nYour app card has to be named exactly Home Assistant. Not \"HA\" or \"homeassistant\" or \"the smart house thing.\" Exactly that string. Yes, I should make that more flexible someday. For now, that's the deal.
Prefers the Template API (POST /api/template) so HA computes counts server-side. Falls back to /api/states if templates aren't available. Heavier, but works.
Runs on the same Tokio runtime as everything else — won't block your CPU graphs.
\nPair with LXC status: see the HA container is up and you've got four lights on at 2am. Investigate that later.
\n", "url": "https://boubli.github.io/AMUD-Dashboard/blog/home-assistant-dashboard-card", "title": "Home Assistant Stats on Your Dashboard (Not Just a Link to :8123)", "summary": "Name your app card Home Assistant, drop in a long-lived token, get lights/switches/temp on the card.", "date_modified": "2026-01-24T00:00:00.000Z", "author": { "name": "Youssef Boubli", "url": "https://github.com/boubli" }, "tags": [ "Integrations", "Homelab" ] }, { "id": "https://boubli.github.io/AMUD-Dashboard/blog/plex-jellyfin-live-badges", "content_html": "\"Is anyone watching something right now or can I restart the container?\"
\nThat's the question I wanted answered from the dashboard, not from opening Plex on my phone.
\nSettings → Integrations
\nJellyfin: base URL + API key from Dashboard → Advanced → API Keys.
\nPlex: base URL + X-Plex-Token. If you've never extracted a Plex token before, welcome to the club — there's a few documented ways and they're all mildly annoying.
Starts as CHECKING..., then shows the active stream title. Multiple clients? You'll see something like Dune (+2 more).
Missing creds → NOT CONFIGURED. Fixable in thirty seconds once you stop procrastinating.
\nCard shows Jellyfin is RUNNING and someone's watching Blade Runner. Now you know restarting would make someone mad. That's operational awareness, not just bookmarks.
\nAPI keys get AES-GCM encrypted in SQLite at rest. Not sitting in plain text in a yaml file on disk.
\nDetails: /docs/configuration
", "url": "https://boubli.github.io/AMUD-Dashboard/blog/plex-jellyfin-live-badges", "title": "See What's Playing on Plex and Jellyfin Without Opening the App", "summary": "AMUD Dashboard polls /Sessions and /status/sessions in the background. Your media cards show live stream titles.", "date_modified": "2026-01-22T00:00:00.000Z", "author": { "name": "Youssef Boubli", "url": "https://github.com/boubli" }, "tags": [ "Integrations", "Homelab" ] }, { "id": "https://boubli.github.io/AMUD-Dashboard/blog/docker-homelab-35mb", "content_html": "Not everyone runs Proxmox. Some of you are Docker-all-the-way-down and that's fine.
\nAMUD Dashboard in Docker is two containers:
\namud_app — web server + SQLiteamud_agent — telemetry, mounts Docker socket read-onlyThey talk over a shared volume at /var/run/amud/amud.sock. Same IPC model as bare metal, just containerized.
services:
app:
image: tradmss/amud-dashboard:latest
ports:
- \"8000:8000\"
environment:
- AMUD_AGENT_SECRET=use-a-long-random-string-here
- DB_PATH=/app/data/amud.db
- AMUD_SOCKET_PATH=/var/run/amud/amud.sock
volumes:
- ./data:/app/data
- amud_run:/var/run/amud
agent:
image: tradmss/amud-dashboard:latest
entrypoint: [\"/app/amud-agent\"]
environment:
- AMUD_AGENT_SECRET=use-a-long-random-string-here
- AMUD_DOCKER=1
- AMUD_SOCKET_PATH=/var/run/amud/amud.sock
volumes:
- amud_run:/var/run/amud
- /var/run/docker.sock:/var/run/docker.sock:ro
volumes:
amud_run:
The secret must match in both containers. I cannot count how many issue reports were just mismatched AMUD_AGENT_SECRET.
Link app cards to container names for running/stopped badges.
\nFull guide: /docs/installation/docker
\nRAM lands around 35–100MB depending on host. Still lighter than most PHP/Node dashboards I've run.
", "url": "https://boubli.github.io/AMUD-Dashboard/blog/docker-homelab-35mb", "title": "Docker Homelab Monitoring in ~35MB RAM", "summary": "Two containers, one shared socket volume, AMUD_DOCKER=1 on the agent. Not Proxmox-native but still lean.", "date_modified": "2026-01-20T00:00:00.000Z", "author": { "name": "Youssef Boubli", "url": "https://github.com/boubli" }, "tags": [ "Docker", "Homelab", "Self-Hosted" ] }, { "id": "https://boubli.github.io/AMUD-Dashboard/blog/lxc-status-badges", "content_html": "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.
\nAMUD Dashboard app cards can bind to a Proxmox CTID. Badge flips between RUNNING, STOPPED, and the eternal CHECKING... when something's misconfigured.
\namud-agent running on the Proxmox hostThat's it. If you're stuck on CHECKING..., 90% of the time it's the token. I wrote a whole troubleshooting post for that misery.
\nIf your API role includes VM.PowerMgmt, admins get start/stop/restart on linked containers. Handy when you're on your phone and don't want the Proxmox mobile experience.
Guest users see status only. No accidental pct stop from the kitchen tablet.
Create a restricted amud@pve user with VM.Audit, Sys.Audit, and optionally VM.PowerMgmt. Paste that token into AMUD. Your dashboard doesn't need god-mode PVE access.
Config details: /docs/configuration
", "url": "https://boubli.github.io/AMUD-Dashboard/blog/lxc-status-badges", "title": "Green and Red LXC Badges (Plus Start/Stop From the Dashboard)", "summary": "Link an app card to a CTID, get live RUNNING/STOPPED status, and optionally power-cycle containers without opening Proxmox.", "date_modified": "2026-01-18T00:00:00.000Z", "author": { "name": "Youssef Boubli", "url": "https://github.com/boubli" }, "tags": [ "Proxmox", "Homelab" ] } ] }