Continuity runbook: Local stack
Open
Nobody has claimed this yet.
existing-maintainers-only
- Dominant language
- Python
- Stars
- 180
- Forks
- 137
- Avg merge
- 3d 23h
- Merged PRs (30d)
- 21
Description
Task
A second maintainer can bring up the laptop stack (pgvector Postgres, Neo4j, Redis, migrations) via Makefile so they can reproduce prod failures and run import/GA backfill.
Success criteria
-
make docker-postgres(pgvector, not plainpostgres),docker-neo4j,docker-redis,make migrate-upgrade - Does not point
CRE_CACHE_FILEat Heroku - Knows volume reset targets (
make docker-*-rm) - Runbook
docs/continuity/runbooks/local-stack.md(skillcontinuity-local-stack)
Context
AGENTS.mdlocal docker section; README local install- Required before catalog import and GA backfill runbooks
Constraints
- existing maintainers only (ops reproduction, not a public getting-started rewrite)
- Do not commit surprise
make frontendbundle.jschanges
Agent prompt
See Agent prompt in docs/continuity/runbooks/local-stack.md.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the Makefile, AGENTS.md local Docker section, README local install guidance, and the Agent prompt in docs/continuity/runbooks/local-stack.md. Verify the runbook covers the pgvector Postgres, Neo4j, Redis, migration, Heroku cache, and volume-reset targets, plus the frontend-change constraint; done means a second maintainer can reproduce the local stack and backfill prerequisites.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, postgresql, redis
- Domain
- databases, devops, documentation
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Clearly specified
- Newbie friendliness
- 65/100