nntrivi2001
61cc37ba32
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).
36 lines
1.2 KiB
Bash
Executable File
36 lines
1.2 KiB
Bash
Executable File
#!/usr/bin/env bash
|
|
# Dev-container bootstrap. Installs all workspace dependencies. Runs once,
|
|
# after the container is created.
|
|
#
|
|
# Deliberately does NOT install Claude Code hooks: hooks are a host-side concern
|
|
# (issue #193) and `scripts/install-hooks.js` refuses to run inside a container.
|
|
# @author Nguyễn Ngọc Trí Vĩ <vinnt@smartgift.vn>
|
|
set -euo pipefail
|
|
|
|
echo "▶ Installing server + client dependencies (npm run setup)…"
|
|
npm run setup
|
|
|
|
cat <<'EOF'
|
|
|
|
✅ Dev environment ready.
|
|
|
|
Develop:
|
|
npm run dev # server on :4820 + Vite client on :5173
|
|
npm start # production-style server (serves client/dist)
|
|
|
|
Test:
|
|
npm run test:server # node --test
|
|
npm run test:client # vitest
|
|
|
|
Docs:
|
|
npm run openapi:yaml # regenerate openapi.yaml from the live spec
|
|
|
|
⚠ Claude Code hooks are HOST-side. Do NOT run `npm run install-hooks` in this
|
|
container — it is refused on purpose (issue #193). Run it on your HOST so the
|
|
hook handler path exists there and POSTs to http://localhost:4820 (forwarded
|
|
from this container).
|
|
|
|
Electron desktop builds (npm run desktop:*) also need a host with a display
|
|
and are not supported inside this container.
|
|
EOF
|