v0.0.11
Diagrid Dev Dashboard
A local dashboard for Dapr developers that offers a live view of everything Dapr running on your machine, plus guided builders for authoring Dapr component and resiliency YAML. Where v0.0.10 turned the dashboard toward the integration-testing workflow (Testcontainers discovery, sidecar workflows, MongoDB), v0.0.11 is about focus: a new set of exclusive --mode filters lets you point the dashboard at exactly one way of running Dapr — dapr run, Docker Compose, Testcontainers, or .NET Aspire — and every view follows.
What's new
🎛️ Exclusive --mode discovery filters
--mode dapr-run,--mode compose,--mode test-containers, and--mode aspire(also viaDEVDASHBOARD_MODE) each restrict discovery to a single source — filters are exclusive and never combined. Leave the mode unset and the dashboard performs the complete scan across all sources, exactly as before.- The filter applies to every surface: applications, workflows, state-store detection, the Control Plane view, and the Logs page's target list all follow the selected source.
composeandtest-containersrequire a container runtime and now fail fast at startup with a clear message when docker/podman is missing — no more silently empty dashboard.
🐝 Aspire mode on the host
--mode aspiregains a second life outside the AppHost: run the dashboard as a standalone host process and it filters the local process scan down to Aspire-managed apps (detected via the Aspire DCP proxy). Inside an AppHost-managed container (theDEVDASHBOARD_APP_*contract), everything behaves exactly as inv0.0.9.
🎚️ Mode-aware Control Plane & Logs
- The Control Plane view shows only the family that matches your mode — the
dapr initcontainers fordapr-run/aspire, compose-run placement/scheduler forcompose— and its start/stop/restart and log-stream actions are gated the same way. - Empty states now tell the truth per mode instead of always suggesting
dapr init, and the Logs page no longer offersdapr_*log targets in modes where they don't apply. - Bonus fix: with no control-plane services enabled, the dashboard no longer runs a bare
docker statsthat sampled every container on the machine each poll.
🏷️ "Mode" column
- The Applications table's Run template column is now Mode, showing where each app came from with friendly names — Dapr run, Compose, TestContainers, Aspire — and the run-template name preserved as a tooltip. App detail gains a matching Mode row.
📚 Docs
- The README documents the new mode switch, and
ARCHITECTURE.mdnow covers the mode-driven source selection and the capabilities layer (how one binary serves host and container postures with different feature sets). go installbuilds now embed the pre-built SPA, so the binary works out of the box without a local frontend build.
Install & run
One-liner (macOS / Linux):
curl -sSL https://raw.githubusercontent.com/diagridio/dev-dashboard/main/scripts/install.sh | shWindows (PowerShell):
iwr -useb https://raw.githubusercontent.com/diagridio/dev-dashboard/main/scripts/install.ps1 | iexWith Go (≥ 1.26):
go install github.com/diagridio/dev-dashboard@v0.0.11Container:
docker pull ghcr.io/diagridio/dev-dashboard:0.0.11Run:
dev-dashboard # complete scan, http://localhost:9090
dev-dashboard --mode compose # only what Docker Compose is runningSingle self-contained binary — the React frontend is embedded via go:embed, so there are no runtime dependencies. Prebuilt archives for macOS and Linux (amd64 + arm64) and Windows (amd64) are attached below, and the multi-arch container image is on GHCR.