feat(mcp): ship yt mcp serve as Docker only, drop systemd #124
Loading…
Reference in a new issue
No description provided.
Delete branch "feat/YT-72-mcp-docker-only-deprecate-systemd"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Remove the systemd deployment path for the MCP HTTP service and settle the container as the single supported way to run
yt mcp serve. Theyt mcp service install/uninstallcommand andcrates/yt-cli/src/commands/mcp/service.rsare deleted, so nothing renders a systemd user unit or an on-diskmcp.envanymore. With the only key generator gone, the two symmetric keys are never generated: the operator mints them and the service already fails at startup (Crypto::from_env/SessionSigner::from_env) with an actionable message when either is missing or does not decode to 32 bytes.compose.mcp.ymlis now the documented deployment, configured entirely by environment variables, with resources prefixedyoutrack-mcp-(serviceyoutrack-mcp, volumeyoutrack-mcp-data, networkyoutrack-mcp-private) and the SQLite state on the named volume. The runtime image defaultsYOUTRACK_MCP_DATABASE_URLtosqlite:///data/youtrack-mcp.dbso state persists on that volume even when the variable is unset.docs/deployment.mdis rewritten around the container (key generation and custody, reverse-proxy TLS, volume persistence, first-admin bootstrap) and gains an upgrade section telling operators to stop and disable the old systemd unit themselves;CHANGELOG.mdcarries the same removal note for the release notes.yt mcp stdiois untouched. A new CLI test (mcp_service_subcommand_is_gone) fails ifyt mcp servicereappears, and the now-unused optionalbase64/randdependencies are dropped fromyt-cli.#YT-72