May 3, 2026
WebDash as personal infrastructure
A short note on the tool I built to keep my projects buildable, runnable, and less dependent on remembered shell trivia.
I spent part of my spare time building a tool called WebDash.
Despite the name, it is not really about the web. The problem it solves is simpler: every project accumulates commands, environment assumptions, ports, and local rituals. After a while, the real cost is not the commands themselves but the mental overhead of remembering how everything is supposed to run.
WebDash lets me define project commands once and execute them in a consistent way. It acts like a lightweight layer over the build and runtime workflow, with support for dependencies, environment setup, and recurring tasks.
That makes it useful as personal infrastructure. I can move between projects without reconstructing the rules from scratch each time, and I can encode the boring parts in configuration instead of memory.
The repository is public here:
One of the more useful aspects is that the configuration is concrete enough to serve as documentation. When a project knows how to build itself, start itself, and report its own status, it becomes easier to trust and easier to revisit.