chore: remove unused surfaces (VS Code extension, statusline, landing assets, Docker)

The repo shipped five install/publish surfaces that nothing in the project builds, tests or documents as supported any more. Each one carried its own stale docs, and the Docker/Podman path additionally described a Dockerfile whose COPY of statusline/ would have broken the build the moment that directory went away. Removed: vscode-extension/ (16 files, marketplace extension for an ID we do not own); statusline/ (3 files, standalone CLI statusline); the repo-root landing/wiki PWA assets (sw.js, manifest.json, robots.txt, sitemap.xml, og-image.svg, favicon.svg, fonts/ - 17 files for pages that no longer exist); .superpowers/ (4 files of scratch brainstorm state, already covered by .gitignore:55); and the container publish path (Dockerfile, docker-compose.yml, .dockerignore, 5 Makefile targets, 2 npm scripts). Kept deliberately - these are about the USER's containers, not ours: scripts/install-hooks.js container detection and AGENTHUB_ALLOW_CONTAINER_HOOKS (issue #193), server/lib/lane-detect.js docker-compose service detection, server/data/profile-templates/postgres-compose/, server/lib/stage-detect.js 'docker push' detection, the host.docker.internal Prometheus notes, the Config Explorer's reads of the user's own ~/.claude/statusline.py, and .devcontainer/ (its docker-in-docker feature is dropped since it existed only to build the removed Dockerfile). Docs follow the code: ARCHITECTURE.md loses the VS Code, statusline and container sections plus two dead TOC anchors, and its PWA section is rewritten from three PWAs to one; INSTALL.md, SETUP.md, docs/DEPLOYMENT.md, server/README.md, client/README.md, docs/README.md, docs/HOOKS.md and docs/DATABASE.md drop the same. The Makefile target count in ARCHITECTURE.md is corrected 25 -> 17 (it was already stale).
2026-09-10 13:44:28 +07:00
parent e972267a42
commit 61cc37ba32
65 changed files with 60 additions and 6626 deletions
@@ -64,7 +64,7 @@ graph TB
 ```

 **Database Location:**
- **Canonical (default):** `~/.claude/agenthub/dashboard.db` — shared by `npm start`, `npm run dev`, Docker (bind mount), and the desktop app when it uses the same data dir
+- **Canonical (default):** `~/.claude/agenthub/dashboard.db` — shared by `npm start`, `npm run dev`, and the desktop app when it uses the same data dir
 - **Override:** set `DASHBOARD_DATA_DIR` (directory) or `DASHBOARD_DB_PATH` (file path) for tests or custom deployments
 - **Legacy:** repo-local `./data/dashboard.db` is migrated into the canonical location on first launch (see `server/db.js`)
 - **Pre-rebrand:** an install that predates AgentHub keeps its data in `~/.claude/agent-dashboard/`. Server startup renames that directory to `~/.claude/agenthub/` once, before anything opens the database (`migrateLegacyDataDir()` in `server/lib/claude-home.js`). It is a same-filesystem rename, so it is instant even at multiple gigabytes and never leaves two copies. If the rename fails, or `DASHBOARD_DATA_DIR` is set, nothing moves and the old directory keeps being used.
@@ -10,7 +10,6 @@ Enterprise deployment strategies for Agent Dashboard across development, staging
 - [Deployment Architecture](#deployment-architecture)
 - [Local Development](#local-development)
 - [Production Deployment](#production-deployment)
- [Docker Deployment](#docker-deployment)
 - [Cloud Deployment](#cloud-deployment)
 - [Process Management](#process-management)
 - [Monitoring & Logging](#monitoring--logging)
@@ -26,7 +25,6 @@ Enterprise deployment strategies for Agent Dashboard across development, staging
 Agent Dashboard supports multiple deployment modes:

 - **Local Development** - Hot reload for rapid iteration
- **Docker** - Containerized deployment with Docker/Podman
 - **PM2** - Process management for production
 - **Systemd** - System service on Linux
 - **Cloud** - Deploy to AWS, Azure, GCP, or other cloud providers
@@ -35,7 +33,6 @@ Agent Dashboard supports multiple deployment modes:
 graph TB
    subgraph "Deployment Modes"
        Dev[Local Development<br/>npm run dev]
-        Docker[Docker Container<br/>docker compose up]
        PM2[PM2 Process Manager<br/>pm2 start]
        Systemd[Systemd Service<br/>systemctl start]
        Cloud[Cloud Platform<br/>Kubernetes, ECS, etc.]
@@ -48,8 +45,6 @@ graph TB
    end
    
    Dev --> DevEnv
-    Docker --> DevEnv
-    Docker --> StagingEnv
    PM2 --> ProdEnv
    Systemd --> ProdEnv
    Cloud --> ProdEnv
@@ -260,118 +255,14 @@ CODEX_HOME=                             # where Codex keeps sessions/ (default ~
 LOG_LEVEL=info                         # debug | info | warn | error
 ```

-> **Reverse-proxy / Docker exposure:** the app binds loopback, so publish it to a
+> **Reverse-proxy / container exposure:** the app binds loopback, so publish it to a
 > network only through a proxy you control that adds TLS + auth, or set
-> `DASHBOARD_HOST=0.0.0.0` **with** `DASHBOARD_TOKEN`. A `-p 4820:4820` Docker
-> mapping assumes a trusted host network — do not expose it publicly without a
+> `DASHBOARD_HOST=0.0.0.0` **with** `DASHBOARD_TOKEN`. A published `4820` port
+> assumes a trusted host network — do not expose it publicly without a
 > token and a proxy.

 ---

-## Docker Deployment
-
-### Docker Compose (Recommended)
-
-```yaml
-# docker-compose.yml
-version: '3.8'
-
-services:
-  agenthub:
-    build: .
-    ports:
-      - "4820:4820"
-    volumes:
-      - ./data:/app/data
-    environment:
-      - NODE_ENV=production
-      - PORT=4820
-    restart: unless-stopped
-    healthcheck:
-      test: ["CMD", "curl", "-f", "http://localhost:4820/api/sessions"]
-      interval: 30s
-      timeout: 10s
-      retries: 3
-      start_period: 40s
-```
-
-### Build & Run
-
-```bash
-# Build image
-docker compose build
-
-# Start container
-docker compose up -d
-
-# View logs
-docker compose logs -f
-
-# Stop container
-docker compose down
-```
-
-### Multi-Stage Dockerfile
-
-```dockerfile
-# Build stage
-FROM node:22-alpine AS builder
-
-WORKDIR /app
-
-# Install dependencies
-COPY package*.json ./
-COPY client/package*.json ./client/
-RUN npm ci && cd client && npm ci
-
-# Build client
-COPY client ./client
-RUN cd client && npm run build
-
-# Production stage
-FROM node:22-alpine
-
-WORKDIR /app
-
-# Copy built artifacts
-COPY --from=builder /app/client/dist ./client/dist
-COPY --from=builder /app/node_modules ./node_modules
-COPY server ./server
-COPY package.json ./
-
-# Create data directory
-RUN mkdir -p /app/data
-
-EXPOSE 4820
-
-HEALTHCHECK --interval=30s --timeout=10s --start-period=40s --retries=3 \
-  CMD node -e "require('http').get('http://localhost:4820/api/sessions', (res) => process.exit(res.statusCode === 200 ? 0 : 1))"
-
-CMD ["node", "server/index.js"]
-```
-
-### Container Architecture
-
-```mermaid
-graph TB
-    subgraph "Docker Host"
-        subgraph "Container"
-            App[Node.js App<br/>:4820]
-            Volume[Volume Mount<br/>/app/data]
-        end
-    end
-    
-    Host[Host Filesystem<br/>./data] -->|Bind Mount| Volume
-    App --> Volume
-    
-    Client[External Clients] -->|Port 4820| App
-    
-    style App fill:#2496ED,color:#fff
-    style Volume fill:#FFA500
-```
-
---
-
 ## Cloud Deployment

 ### AWS (Elastic Beanstalk)
@@ -395,6 +286,9 @@ eb open

 ### Kubernetes

+The repo ships no container image or `Dockerfile` — build your own from
+`npm ci && npm run build` and push it to your registry, then reference it here.
+
 ```yaml
 # k8s/deployment.yaml
 apiVersion: apps/v1
@@ -603,19 +497,16 @@ graph TB
    subgraph "Log Aggregation"
        Stdout --> PM2[PM2 Logs]
        Stdout --> Systemd[Systemd Journal]
-        Stdout --> Docker[Docker Logs]
    end
    
    subgraph "Monitoring Tools"
        PM2 --> File[Log Files]
        Systemd --> Journalctl[journalctl]
-        Docker --> DockerLogs[docker logs]
    end
    
    subgraph "Analysis"
        File --> Splunk[Splunk/ELK]
        Journalctl --> Splunk
-        DockerLogs --> Splunk
    end
    
    style App fill:#000000,color:#fff
@@ -912,7 +803,7 @@ NODE_ENV=development node server/index.js

 This deployment guide covers:

- ✅ **Multiple deployment modes** - Local, Docker, PM2, Systemd, Cloud
+- ✅ **Multiple deployment modes** - Local, PM2, Systemd, Cloud
 - ✅ **Production best practices** - Environment variables, health checks, logging
 - ✅ **Process management** - PM2, systemd service files
 - ✅ **Monitoring & logging** - Metrics endpoint, log aggregation
@@ -578,8 +578,8 @@ function sendToServer(hookType, payload) {
 >    Each server appends its `{port, pid, startedAt, dataDir}` entry on
 >    startup and removes it on a clean shutdown. The handler **prunes any
 >    entry whose PID is no longer alive** and POSTs the hook payload to one
->    port per **unique SQLite data directory** (lowest port wins when Docker
->    and `npm run dev` share `~/.claude/agenthub`).
+>    port per **unique SQLite data directory** (lowest port wins when two
+>    instances share `~/.claude/agenthub`).
 > 3. If neither yields a target, the handler falls back to `4820`.
 >
 > Dashboards with **different** databases (e.g. the packaged desktop app using
@@ -429,7 +429,7 @@ This documentation covers:

 - ✅ **Complete architecture** - Frontend, backend, database, integrations
 - ✅ **API reference** - REST endpoints, WebSocket events
- ✅ **Deployment guides** - Docker, PM2, systemd, cloud
+- ✅ **Deployment guides** - PM2, systemd, cloud
 - ✅ **Performance tuning** - Database, server, client optimizations
 - ✅ **Integration guides** - Hooks, MCP, custom clients
 - ✅ **Internationalization** - Language resources, switching flow, locale formatting, rollout checklist