Continuity runbook: Restart production
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 restart Heroku dynos for production (opencreorg) — the “restart the server” easy-fix — using the continuity runbook.
Success criteria
- Dry-run or real restart recorded:
heroku psbefore/after, which process types (web/worker/ both) - Homepage
https://www.opencre.org/returns HTTP 200 (or next runbook named if not) - Followed
docs/continuity/runbooks/restart-production.md(skillcontinuity-restart-production) - No secrets in comments
Context
Procfile:webgunicorn,workercre.py --start_worker- Prefer restart before rollback if the current release was previously healthy
Constraints
- existing maintainers only
- Confirm app name before
heroku ps:restart(defaultopencreorg, nottmp-cre) - Do not rollback, deploy, or change config in this ticket
Agent prompt
See Agent prompt in docs/continuity/runbooks/restart-production.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/restart-production.md and its Agent prompt first, then check Procfile for the web and worker process types. Follow the runbook for the confirmed Heroku app, record heroku ps before and after, verify the homepage returns HTTP 200, and ensure no secrets are included.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- cloud, devops
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Active
- Clarity
- Clearly specified
- Newbie friendliness
- 38/100