stack
Skill5 starsChanged 10 days agoMITView on GitHub
Bring up the local Postgres, Mongo and MySQL stack the gateway and its tests run against. Use for dev stack, bin/dev, state db, target db, mongo.
8 other projects use a version of this.
Adopted by
Most recently taken up by
- shipshitdev/skillstheir own version, first seen Nov 1, 2026
- abgmgp/simple-agentic-project-templatetheir own version, first seen Oct 20, 2026
- Nonetss/colofontheir own version, first seen Oct 17, 2026
- mikhin/claude-skillstheir own version, first seen Oct 13, 2026
- bionic-gpt/bionic-gpttheir own version, first seen Oct 8, 2026
- guardana/guardanatheir own version, first seen Oct 8, 2026
Used with
Projects with it also use review.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
SentrySkillreview
Fixture review skill.
Also in 3 projects that use this
Other versions8 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 8
- bionic-gpt/bionic-gpt★ 2.4ksame name
- guardana/guardana★ 203same name
- shipshitdev/skills★ 39same name
- luisabwk/kraken★ 1same name
- abgmgp/simple-agentic-project-template★ 0same name
- jorekai/skills★ 0same name
- mikhin/claude-skills★ 0same name
- Nonetss/colofon★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository4 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- state-migrationsSkill
- verify-changeSkill
The file
We split this skill into the rules it gives an agent
2 rules. 0 are common, 0 are distinctive, and 2 are very specific to this project.
0
Common
Most of the 7 edited versions we read keep these.
0
Distinctive
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 10
Run the suite against it: bin/test (it always runs docker compose -f docker-compose.dev.yml up -d --wait first — even when the stack is …
- Very specific: line 12
Stop the stack without losing data: bin/dev down removes the containers, the volumes stay.
“Common” is measured: kept by at least 6 in 10 of the 7 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
House skill — established by dz-runner setup mode from this repo's own evidence, then owned by its maintainers. Correct it in place; setup never overwrites a skill that exists.
- Bring the stack up:
bin/dev up— it runsdocker compose -f docker-compose.dev.yml up -d --waitand starts state-db (localhost:5433), target-db (localhost:5434), target-mongo (localhost:27018) and permissions-mysql (localhost:3307). fail -> a container never became healthy:docker compose -f docker-compose.dev.yml psthendocker compose -f docker-compose.dev.yml logs <service>. - Confirm health:
docker compose -f docker-compose.dev.yml psmust show every servicehealthy. The integration tests hard-code these ports; changing them means changing the fallback URLs intests/*.rs. - Run the suite against it:
bin/test(it always runsdocker compose -f docker-compose.dev.yml up -d --waitfirst — even when the stack is already up — and waits for all four services to become healthy; a service that never becomes healthy returns 75 without running cargo) or one file withbin/test --test run_query_e2e. - Inspect a database by hand:
bin/dev psql state(gateway state — sessions, audit_calls) orbin/dev psql target(the example target DB). - Stop the stack without losing data:
bin/dev downremoves the containers, the volumes stay. Onlydocker compose -f docker-compose.dev.yml down -vwipes the volumes, and only when a test needs a virgin database. - Boot the gateway against it: write the minimal config from
website/docs/deployment/quickstart.md§"Run it locally" toconfig/local.yaml(gitignored) — one server onlocalhost:5434,tls: insecure,password: ${ENV:TARGET_DB_PASSWORD}— thenTLS_DISABLED=true cargo run -- --config config/local.yaml. fail -> the log never shows "state DB connected, migrations applied", so the state-DB migration failed; checkbin/dev psql state. - Smoke the endpoint:
curl -s -o /dev/null -w '%{http_code}\n' -X POST http://127.0.0.1:8443/mcp -H 'content-type: application/json' -d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{}}'—401means the MCP endpoint and the auth gate are live; anything else means the process is not serving.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.