feat(maestro): add a nix flake and Home Manager module
Ships `maestro`, `maestro-web` and the SPA bundle as flake packages, plus a `services.maestro` Home Manager module that runs the daemon and the web UI as systemd user services. `maestro-web`'s build.rs now honours MAESTRO_WEB_DIST and hands the resolved bundle path to `include_dir!` through MAESTRO_WEB_BUNDLE_DIR. Without it the Nix build would have to run `pnpm install` mid-compile, which the sandbox has no network for. Unset, the pnpm path is unchanged. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
This commit is contained in:
co-authored by
Claude Opus 5
parent
c856333e4a
commit
401afbc812
@@ -49,6 +49,55 @@ The wizard:
|
||||
|
||||
The binary lands in `~/.cargo/bin/maestro` — make sure that's on your `$PATH`.
|
||||
|
||||
## Nix / NixOS
|
||||
|
||||
The repo is a flake. It exposes two packages and a Home Manager module:
|
||||
|
||||
```sh
|
||||
nix run git+https://git.naps.pt/naps62/maestro -- list # the maestro binary
|
||||
nix build git+https://git.naps.pt/naps62/maestro#maestro-web
|
||||
```
|
||||
|
||||
`packages.maestro` is the unified CLI + daemon + TUI binary, wrapped so `tmux`
|
||||
and `git` are on its `PATH`. `packages.maestro-web` embeds a prebuilt SPA
|
||||
bundle — the Nix build points `MAESTRO_WEB_DIST` at `packages.webFrontend`, so
|
||||
`build.rs` skips pnpm entirely and no network fetch happens mid-compile. Set
|
||||
that variable yourself to reuse a bundle built elsewhere; leave it unset and
|
||||
the build falls back to running `pnpm install && pnpm build` in `web/`.
|
||||
|
||||
Home Manager, with both services running as *user* units (same trust boundary
|
||||
as the tmux server they wrap):
|
||||
|
||||
```nix
|
||||
{
|
||||
inputs.maestro.url = "git+https://git.naps.pt/naps62/maestro";
|
||||
|
||||
# in your Home Manager configuration:
|
||||
imports = [ inputs.maestro.homeManagerModules.default ];
|
||||
|
||||
services.maestro = {
|
||||
enable = true; # installs the binary, runs `maestro daemon`
|
||||
web.enable = true; # runs `maestro-web`
|
||||
settings = {
|
||||
daemon.bind_addr = "127.0.0.1:7070";
|
||||
web.bind_addr = "0.0.0.0:8081";
|
||||
};
|
||||
};
|
||||
}
|
||||
```
|
||||
|
||||
`settings` is written verbatim to `~/.config/maestro/config.toml` in the schema
|
||||
below; every field has a default, so `{}` writes no file at all. There is no
|
||||
auth layer — bind the web UI to a LAN or VPN address only on a trusted segment,
|
||||
never a public IP.
|
||||
|
||||
`services.maestro.daemon.enable = false` installs the CLI and TUI without
|
||||
running a local daemon, for a host that only talks to another machine's.
|
||||
|
||||
The daemon unit carries the same `KillMode=process` as the wizard-written one,
|
||||
so `systemctl --user restart maestro-daemon` leaves the tmux server and every
|
||||
session alive.
|
||||
|
||||
## Thin builds for single-role hosts
|
||||
|
||||
The default install pulls in everything (`cli` + `daemon` + `tui`). Single-role
|
||||
|
||||
Reference in New Issue
Block a user