Continuity runbook: Production DB backup
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 capture a completed on-demand Heroku Postgres backup for opencreorg via scripts/db/backup-opencreorg.sh.
Success criteria
- Wrapper exits 0;
heroku pg:backupsshows newest backup Completed - Issue comment has backup id + time only (no credentialed URLs)
- Runbook
docs/continuity/runbooks/production-db-backup.md(skillcontinuity-production-db-backup)
Context
- Daily capture also exists in
.github/workflows/backup.yml; this ticket is the manual path scripts/db/common.shalways waits for the capture to finish
Constraints
- existing maintainers only
- Do not set
BACKUP_MANDATORY=0 - Do not commit dump files
Agent prompt
See Agent prompt in docs/continuity/runbooks/production-db-backup.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 docs/continuity/runbooks/production-db-backup.md and its Agent prompt first, then inspect scripts/db/backup-opencreorg.sh, scripts/db/common.sh, and .github/workflows/backup.yml. Follow the documented manual path with an existing maintainer and confirm the wrapper exits 0 and heroku pg:backups shows a completed backup. Record only the backup id and time in the issue comment, with no credentialed URLs or dump files.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, postgresql, shell
- Domain
- database, devops, documentation
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Clearly specified
- Newbie friendliness
- 35/100