Miguel PalhasandClaude Opus 5
4fc90aabfb
The browser reached the daemon through maestro-web, a second binary that served the SPA and reverse-proxied /api/* — two TCP connections and a WebSocket frame re-encode on every keystroke and every byte of PTY output. On one machine that hop buys nothing. The daemon now embeds the bundle and serves it off its own listener, behind a default-on `web` feature. `--no-default-features` builds without pnpm or node; MAESTRO_WEB_DIST still takes a prebuilt bundle. The router's fallback answers an unmatched /api/* with 404 rather than the SPA shell, so a client expecting JSON gets a status it can read instead of HTML. Removes maestro-web and the [web] config section. An existing [web] block is ignored, not rejected. The installer deletes a leftover maestro-web.service on upgrade. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
27 lines
694 B
TOML
27 lines
694 B
TOML
[package]
|
|
name = "maestro-protocol"
|
|
version.workspace = true
|
|
edition.workspace = true
|
|
license.workspace = true
|
|
repository.workspace = true
|
|
publish.workspace = true
|
|
description = "Shared wire types for Maestro daemon/client communication"
|
|
|
|
[features]
|
|
default = []
|
|
# Opt-in `reqwest`-backed client. Off by default so `maestro-daemon`, which
|
|
# only needs the wire types and route paths, does not pull an HTTP stack it has
|
|
# no use for.
|
|
client = ["dep:reqwest"]
|
|
|
|
[dependencies]
|
|
chrono.workspace = true
|
|
serde.workspace = true
|
|
serde_json.workspace = true
|
|
thiserror.workspace = true
|
|
uuid.workspace = true
|
|
reqwest = { workspace = true, optional = true }
|
|
|
|
[dev-dependencies]
|
|
serde_json.workspace = true
|