feat(maestro): add a process-compose dev stack (#52)

2026-08-23 10:02:09 +01:00
parent a51809f25a
commit 53660407e3
6 changed files with 175 additions and 3 deletions
@@ -56,12 +56,19 @@ crates/
 ├── maestro-installer/   # `maestro-install` wizard: cargo install + systemd (NAP-225)
 └── maestro-e2e/         # cross-process integration tests (NAP-217)
 web/                     # browser SPA (NAP-218)
-flake.nix                # Nix flake: `maestro`, `maestro-web`, `webFrontend`
+flake.nix                # Nix flake: packages, checks, dev shell, `nix run .#dev`
 nix/                     # Home Manager module (`services.maestro`)
 ```

 See `docs/INSTALL.md` for end-user install instructions.

+`nix run .#dev` (or `just dev`) brings up the whole local stack under
+process-compose: a debug daemon on 127.0.0.1:7071, then Vite on :5173 once the
+daemon answers `/api/info`. The SPA proxies `/api/*` back to the daemon, so only
+the UI is exposed on the network. The dev port is deliberately not the daemon's
+own default 7070 (`devDaemonPort` in `flake.nix`), so the stack never fights a
+real daemon on the same host.
+
 ## Conventions

 - **TDD by default.** Failing test first, then minimal impl. Commit test + impl together.