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.
82 lines
3.2 KiB
JSON
82 lines
3.2 KiB
JSON
{
|
|
// ─────────────────────────────────────────────────────────────────────────
|
|
// Optional, opt-in dev environment for AgentHub.
|
|
// Used only when you choose "Dev Containers: Reopen in Container" (VS Code) or
|
|
// open the repo in a GitHub Codespace. It changes nothing for host-based dev.
|
|
//
|
|
// Covers the full project: the Express server (4820), the React/Vite client
|
|
// (5173) and the VS Code extension. The native `better-sqlite3`
|
|
// addon builds here (build-essential + python3 are installed in the Dockerfile).
|
|
//
|
|
// NOTE (issue #193): Claude Code hooks are a HOST-side concern. This container
|
|
// intentionally does NOT bind-mount ~/.claude and does NOT install hooks — the
|
|
// installer refuses to run inside a container. Run `npm run install-hooks` on
|
|
// your host so hooks POST to http://localhost:4820 (forwarded from here).
|
|
// ─────────────────────────────────────────────────────────────────────────
|
|
"name": "AgentHub",
|
|
"build": {
|
|
"dockerfile": "Dockerfile",
|
|
"context": ".."
|
|
},
|
|
|
|
"features": {
|
|
"ghcr.io/devcontainers/features/github-cli:1": {},
|
|
// Lets you build/run the project's own production Dockerfile + docker-compose
|
|
// from inside the dev container (e.g. to reproduce issue #193 deliberately).
|
|
"ghcr.io/devcontainers/features/docker-in-docker:2": {}
|
|
},
|
|
|
|
// Server (API + WebSocket) and the Vite client dev server. VS Code forwards
|
|
// these from the container's localhost, so the secure loopback bind is fine.
|
|
"forwardPorts": [4820, 5173],
|
|
"portsAttributes": {
|
|
"4820": {
|
|
"label": "Dashboard server (API + WebSocket)",
|
|
"onAutoForward": "notify"
|
|
},
|
|
"5173": {
|
|
"label": "Vite dev client",
|
|
"onAutoForward": "openBrowser"
|
|
}
|
|
},
|
|
|
|
// Install root + client + vscode-extension deps.
|
|
// Never installs Claude Code hooks (host-only — see note above).
|
|
"postCreateCommand": "bash .devcontainer/post-create.sh",
|
|
"waitFor": "postCreateCommand",
|
|
|
|
"remoteUser": "node",
|
|
|
|
// Dev defaults. NODE_ENV=development so `npm run dev` runs API-only with the
|
|
// Vite client on 5173 (production mode would serve the prebuilt client/dist).
|
|
"remoteEnv": {
|
|
"NODE_ENV": "development"
|
|
},
|
|
|
|
"customizations": {
|
|
"vscode": {
|
|
"extensions": [
|
|
"dbaeumer.vscode-eslint",
|
|
"esbenp.prettier-vscode",
|
|
"vitest.explorer",
|
|
"ms-azuretools.vscode-docker",
|
|
"redhat.vscode-yaml",
|
|
"yzhang.markdown-all-in-one",
|
|
"ms-python.python",
|
|
"bradlc.vscode-tailwindcss",
|
|
"GitHub.vscode-pull-request-github"
|
|
],
|
|
"settings": {
|
|
"editor.formatOnSave": true,
|
|
"editor.defaultFormatter": "esbenp.prettier-vscode",
|
|
"editor.codeActionsOnSave": {
|
|
"source.fixAll.eslint": "explicit"
|
|
},
|
|
"eslint.validate": ["javascript", "javascriptreact", "typescript", "typescriptreact"],
|
|
"files.eol": "\n",
|
|
"terminal.integrated.defaultProfile.linux": "bash"
|
|
}
|
|
}
|
|
}
|
|
}
|