nntrivi2001
c7dbaf2d9f
Two leftovers from the rebrand, done together because they touch the same docs and manifests. **Data directory.** `agent-dashboard` could not simply be renamed in the source: it names a real directory holding the live SQLite database. Startup now moves it once, via `migrateLegacyDataDir()` in `server/lib/claude-home.js` — a same-filesystem rename, so it is instant even at multiple gigabytes and cannot leave two divergent copies. `getDataDir()` stays PURE and resolves to the legacy path until the move happens; the first version of this put the rename inside the getter, which meant `npm run test:server` relocated the developer's real database as a side effect. The call sits behind `require.main === module` and ahead of the router requires, because those pull in db.js, which opens SQLite at module load. A failed rename is silent and the old directory keeps being used: an unfashionable directory name beats a blank database beside an unreachable one. Same treatment for the port-discovery file (`.agent-dashboard.json` → `.agenthub.json`, old one dropped on write). Not renamed on purpose: the Sagi localStorage keys (renaming silently resets everyone's prefs) and the PWA manifest `id` (changing it orphans an installed app). **MCP server.** 4 tool calls in 46 days across 577,132 events, against 4,556 lines of TypeScript, a 2 MB committed build artifact, and a pre-commit guard that had already blocked commits twice. Deleted: `mcp/`, the maintainer skills and `mcp-reviewer` agent, the build check, `plugins/agenthub/.mcp.json`, `docs/MCP.md`, 12 npm scripts, 5 Makefile targets, and every doc section describing it. Kept, because they are unrelated things sharing the name: the Config Explorer's MCP tab and its API, per-lane Playwright MCP, the agenthub-config plugin's MCP audit, and the historical `mcp__plugin_agenthub_*` events that analytics must keep attributing. Verified: server 1432/1432, client 459/459, tsc clean, prettier clean. Both directions of the migration proven — a sandbox-HOME test run leaves the legacy directory untouched, and a real boot moves it with its contents intact.
24 lines
1.1 KiB
YAML
24 lines
1.1 KiB
YAML
services:
|
|
agent-monitor:
|
|
build: .
|
|
container_name: agent-monitor
|
|
ports:
|
|
# Publish on the host loopback only, so the dashboard is not reachable
|
|
# from the LAN out of the box (matches the server's default trust
|
|
# boundary — GHSA-gr74-4xfh-6jw9). To expose it on a LAN, change this to
|
|
# "${DASHBOARD_PORT:-4820}:4820" and set DASHBOARD_TOKEN below.
|
|
- "127.0.0.1:${DASHBOARD_PORT:-4820}:4820"
|
|
volumes:
|
|
# Same SQLite file as `npm start` / `npm run dev` on the host.
|
|
- ${CLAUDE_HOME:-~/.claude}/agenthub:/app/data
|
|
- ${CLAUDE_HOME:-~/.claude}:/root/.claude:ro
|
|
environment:
|
|
- NODE_ENV=production
|
|
- DASHBOARD_PORT=4820
|
|
# Optional — required when a Prometheus-in-Docker scraper reaches this
|
|
# container as anything other than loopback (e.g. host.docker.internal).
|
|
- DASHBOARD_ALLOWED_HOSTS=${DASHBOARD_ALLOWED_HOSTS:-}
|
|
# DASHBOARD_HOST=0.0.0.0 and DASHBOARD_DATA_DIR=/app/data are baked into
|
|
# the image (see Dockerfile) so both `docker run` and Compose work as-is.
|
|
restart: unless-stopped
|