feat(mcp): ship HTTP server as Docker-only, drop systemd path

Claude-Run commented

2026-07-18 18:47:14 +02:00

Member

Remove fj mcp service install / uninstall and crates/fj/src/mcp/service.rs: the systemd unit baked in Forgejo host, a shared bearer token, and a plaintext mcp.env, all of which are gone now that credentials are per-account (FJ-55) and the HTTP transport is env-only. The MCP subcommand tree keeps serve and stdio only, with a test that asserts service cannot reappear.

Add compose.mcp.yml as the single supported deployment for the multi-user HTTP web service: it builds the runtime image, runs fj mcp serve with FORGEJO_MCP_TRANSPORT=http, publishes on loopback for a reverse proxy, and persists the SQLite state store on the named volume forgejo-mcp-data (service forgejo-mcp, network forgejo-mcp-private). Configuration is environment-only; .env.example lists every variable the service reads and the required master/session keys fail fast if unset.

Confirm the Dockerfile runtime stage serves this deployment: it already runs as non-root appuser, and now creates a writable /app/data volume dir with FORGEJO_MCP_DATABASE_URL defaulting beneath it so state survives restarts.

Add docs/deployment.md documenting only the container path (reverse-proxy TLS, the public base URL contract, volume persistence, key generation and custody, first-admin bootstrap, upgrades) plus the migration steps to stop and disable the removed systemd unit before upgrading. Delete the systemd runbook from README.md and update the stale "no compose stack" notes in CLAUDE.md.

fj mcp stdio is untouched. The startup fail-closed on a missing or malformed master/session key already lives in the HTTP transport (FJ-54) and its tests are unchanged.

#FJ-57

Remove `fj mcp service install` / `uninstall` and `crates/fj/src/mcp/service.rs`: the systemd unit baked in Forgejo host, a shared bearer token, and a plaintext `mcp.env`, all of which are gone now that credentials are per-account (FJ-55) and the HTTP transport is env-only. The MCP subcommand tree keeps `serve` and `stdio` only, with a test that asserts `service` cannot reappear. Add `compose.mcp.yml` as the single supported deployment for the multi-user HTTP web service: it builds the runtime image, runs `fj mcp serve` with `FORGEJO_MCP_TRANSPORT=http`, publishes on loopback for a reverse proxy, and persists the SQLite state store on the named volume `forgejo-mcp-data` (service `forgejo-mcp`, network `forgejo-mcp-private`). Configuration is environment-only; `.env.example` lists every variable the service reads and the required master/session keys fail fast if unset. Confirm the Dockerfile runtime stage serves this deployment: it already runs as non-root `appuser`, and now creates a writable `/app/data` volume dir with `FORGEJO_MCP_DATABASE_URL` defaulting beneath it so state survives restarts. Add `docs/deployment.md` documenting only the container path (reverse-proxy TLS, the public base URL contract, volume persistence, key generation and custody, first-admin bootstrap, upgrades) plus the migration steps to stop and disable the removed systemd unit before upgrading. Delete the systemd runbook from `README.md` and update the stale "no compose stack" notes in `CLAUDE.md`. `fj mcp stdio` is untouched. The startup fail-closed on a missing or malformed master/session key already lives in the HTTP transport (FJ-54) and its tests are unchanged. #FJ-57

Claude-Run added 1 commit

2026-07-18 18:47:14 +02:00

feat(mcp): ship HTTP server as Docker-only, drop systemd path

Check / fmt + clippy + build + tests (pull_request) Successful in 2m53s

Details

Create release / Create release from merged PR (pull_request) Has been skipped

Details

f05883f149

Remove `fj mcp service install` / `uninstall` and `crates/fj/src/mcp/service.rs`: the systemd unit baked in Forgejo host, a shared bearer token, and a plaintext `mcp.env`, all of which are gone now that credentials are per-account (FJ-55) and the HTTP transport is env-only. The MCP subcommand tree keeps `serve` and `stdio` only, with a test that asserts `service` cannot reappear.

Add `compose.mcp.yml` as the single supported deployment for the multi-user HTTP web service: it builds the runtime image, runs `fj mcp serve` with `FORGEJO_MCP_TRANSPORT=http`, publishes on loopback for a reverse proxy, and persists the SQLite state store on the named volume `forgejo-mcp-data` (service `forgejo-mcp`, network `forgejo-mcp-private`). Configuration is environment-only; `.env.example` lists every variable the service reads and the required master/session keys fail fast if unset.

Confirm the Dockerfile runtime stage serves this deployment: it already runs as non-root `appuser`, and now creates a writable `/app/data` volume dir with `FORGEJO_MCP_DATABASE_URL` defaulting beneath it so state survives restarts.

Add `docs/deployment.md` documenting only the container path (reverse-proxy TLS, the public base URL contract, volume persistence, key generation and custody, first-admin bootstrap, upgrades) plus the migration steps to stop and disable the removed systemd unit before upgrading. Delete the systemd runbook from `README.md` and update the stale "no compose stack" notes in `CLAUDE.md`.

`fj mcp stdio` is untouched. The startup fail-closed on a missing or malformed master/session key already lives in the HTTP transport (FJ-54) and its tests are unchanged.

#FJ-57

Claude-Run merged commit 5ffd31c256 into main

2026-07-18 18:50:17 +02:00

Claude-Run deleted branch feat/FJ-57-mcp-docker-only-deployment

2026-07-18 18:50:17 +02:00

Claude-Run referenced this pull request from a commit

2026-07-18 18:50:19 +02:00

Merge pull request 'feat(mcp): ship HTTP server as Docker-only, drop systemd path' (#76) from feat/FJ-57-mcp-docker-only-deployment into main

Rows
Columns

feat(mcp): ship HTTP server as Docker-only, drop systemd path #76