Skip to content
← All articles
Project introduction

DasherControl: a homelab dashboard built around workspaces

Listen to the audio story

DasherControl: one dashboard for your homelab · 1:50 · AI-written script, synthetic voices

Transcript

Ava: Twelve browser tabs, one for every service in your homelab, and you still can't find the right one. Antoine built DasherControl to fix exactly that.

Andrew: So it's a dashboard?

Ava: A dashboard organized around workspaces. A workspace is like a desk: you arrange applets on it, which are bookmarks and embedded applications, and keep a few Docker controls within reach.

Andrew: What's it built with?

Ava: Vue on the front, and Rust with Rocket and Diesel on the back. Behind the dashboard there are two clean paths. Saving a layout goes through workspace handlers into database records.

Andrew: And the second path?

Ava: Container actions. When you restart a container, the request goes through an adapter called Shiplift straight to Docker. The database never touches Docker, and an applet isn't a running container. Keeping those paths apart makes the design easy to reason about.

Andrew: How do workspaces know who they belong to?

Ava: Each workspace has an owner. The handler reads the user's identifier from a token, lists that person's workspaces, and checks the owner before returning the applets inside. So a saved layout belongs to a user, and every applet belongs to a workspace.

Andrew: And Docker?

Ava: One file wraps the Shiplift calls: list containers and images, pull images, create containers, stop or restart them. That keeps the workspace model separate from Docker operations.

Andrew: Can you embed any web app in an applet?

Ava: Many, through iframes. Some apps restrict embedding, so a plain external link sits alongside for those.

Andrew: Is there a demo?

Ava: Yes. The page has a screenshot and the original demo recording showing workspaces and applets in action. The architecture note and the source are linked from the write-up.

DasherControl dashboard screenshot from the project repository
Table of contents

I started DasherControl because my homelab services kept spreading across browser tabs. The idea was a workspace of applets: bookmarks and embedded applications arranged in a dashboard, with a few Docker controls nearby.

1. Two paths behind the same dashboard

flowchart LR
  Dashboard["Dashboard"] --> Workspace["Save workspace"]
  Workspace --> Database[("Workspace records")]
  Dashboard --> Action["Container action"]
  Action --> Docker["Docker via Shiplift"]

Saving a layout goes through workspace handlers and database records. Restarting a container goes through the Shiplift adapter to Docker. PostgreSQL does not execute the Docker action, and an applet is not itself a running container. Keeping those paths separate helps explain both permissions and failure states.

Follow the handlers and Docker boundary in the architecture note.

2. A workspace has an owner

The frontend uses Vue, while the backend uses Rust, Rocket and Diesel. In src/workspaces/handler.rs[1], the list handler reads the tenant identifier from a token. The handler that returns applets checks the workspace’s tenant before returning its contents.

The create-with-applets route also derives the tenant identifier from the token. That is the intended ownership model: a saved layout belongs to a user, and applets belong to a workspace.

The file contains older create and delete paths with different checks. Their presence is a reason to inspect authorization across every operation before using this as a shared service. This article describes an experiment, not a security review of a deployed system.

3. Docker is a separate boundary

src/containers/docker.rs[2] wraps Shiplift calls for listing containers and images, pulling images, creating containers, and stopping or restarting them. This separates the dashboard’s workspace model from Docker operations.

It also exposes a UI problem: the list helpers return an empty vector after a Docker error. An empty dashboard could therefore mean either “nothing is running” or “the service could not be reached.” I would make those states visibly different in a new version.

4. What the browser can embed

The README records iframe login failures. Applications can restrict embedding, and authentication inside a frame may behave differently from an ordinary tab. A dashboard needs an external link for those services even when an iframe works for others.

This is an older project. The repository’s screenshot and optional GIF preserve the interface as it was; they do not demonstrate compatibility with current dependencies.

Play the original demo GIFOriginal DasherControl recording showing workspace and applet interactions

Browse the source and original README[3]. Both illustrations come from its images directory.

References

  1. antoinebou12. (). src/workspaces/handler.rs. [Source file or documentation] github.com.
  2. antoinebou12. (). src/containers/docker.rs. [Source file or documentation] github.com.
  3. antoinebou12. (). DasherControl. [Software repository] github.com.

References use this article’s publication date.