one-clone bootstrap for CIPP monorepo local development, with a code knowledge graph for AI-assisted work.
git clone https://github.com/k-grube/cipp-dev-tools
cd cipp-dev-tools
.\setup.ps1 # forks + clones CyberDrain/CIPP into cipp\, installs pinned graphify, builds the graph
.\dev.ps1 # launches the local dev stack -> http://localhost:5196git clone https://github.com/k-grube/cipp-dev-tools
cd cipp-dev-tools
./setup.sh # forks + clones CyberDrain/CIPP into cipp\, installs pinned graphify, builds the graph
./dev.sh # launches the local dev stack -> http://localhost:5196first setup run builds the code graph cold (a few minutes); pass -SkipGraph / --skip-graph to defer it.
prereqs: PowerShell 7.2+ (pwsh), git, gh (authed), Docker Desktop, node + yarn, python 3. windows also needs Windows Terminal; macos installs pwsh via brew install --cask powershell.
cipp\- monorepo clone, origin = your fork of CyberDrain/CIPP, upstream = CyberDrain (PR-ready)- local dev stack via upstream's own
build\tooling (azurite, Craft api container, module watcher, frontend dev server) graphify-out\graph.json- directed knowledge graph of frontend + backend incl.http_callsedges mapping/api/Xcalls toInvoke-XfunctionsCLAUDE.mdso Claude Code sessions know all of the above
| command | what |
|---|---|
dev.ps1 / dev.sh |
launch the dev environment |
stop.ps1 / stop.sh |
stop the dev stack (compose down, watcher, frontend; azurite data kept) |
graph-tools\update-graph.ps1 / .sh |
refresh the graph after code changes (~10s) |
graph-tools\update-graph.ps1 --cluster |
+ re-cluster and regenerate GRAPH_REPORT.md |
graph-tools\rebuild-graph.ps1 / .sh |
full graph rebuild |
personal docker tweaks: drop a docker-compose.override.yml at the repo root (gitignored), dev.ps1 / dev.sh pick it up.
graphifyyis pinned to 0.9.12 on purpose -spec\graphify-internals.mdexplains what must be re-verified before bumping- fresh clones build an AST+routes graph; doc-derived semantic content needs a one-time
/graphifysession in Claude Code