Continuity runbook: Staging bootstrap
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 bootstrap or refresh Heroku staging with scripts/setup-heroku-staging.sh without ever targeting opencreorg as STAGING_APP.
Success criteria
- Lists required env:
PROD_APP,STAGING_APP,LOCAL_SQLITE_DB - Knows
--embeddings/--gap_analysisvs full sync, and--deleteneedsDESTROY_STAGING - Runbook
docs/continuity/runbooks/staging-bootstrap.md(skillcontinuity-staging-bootstrap) - No env files pasted into GitHub
Context
- Deploy workflow:
.github/workflows/deploy-staging.yml→tmp-crefrom branchstaging - Script copies prod config to staging — treat output as secret
Constraints
- existing maintainers only
- Do not run teardown or full bootstrap in the first drill without named apps and paths
- Never
STAGING_APP=opencreorg
Agent prompt
See Agent prompt in docs/continuity/runbooks/staging-bootstrap.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
Read scripts/setup-heroku-staging.sh and .github/workflows/deploy-staging.yml, then create docs/continuity/runbooks/staging-bootstrap.md. Verify the runbook covers the listed environment variables, sync modes, deletion safeguard, secret-handling rule, named-app/path requirements, and the prohibition on STAGING_APP=opencreorg; do not perform teardown or a full bootstrap.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, shell
- Domain
- devops, documentation
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Clearly specified
- Newbie friendliness
- 45/100