Automate hub deployment in the cluster
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 7.2k
- Forks
- 493
- PR merge metrics
- No merged PRs in 30d
Description
Requirements:
- Tom can deploy a new version of the hub without jack's or victor's help
- If there's an error, it alerts us and aborts the deploy neatly
- We can do this anytime with minimal downtime. we don't have to wait for 3am to deploy
slack convo:
https://lbryians.slack.com/archives/CCVRP9FU4/p1617693917039500?thread_ts=1617655409.039400&cid=CCVRP9FU4
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
No files, tests, or deployment entry points are named. Start by reviewing the current hub deployment process and the linked Slack conversation, then use the requirements—self-service deployment, clean aborts with alerts, and minimal downtime—as the completion criteria.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- devops, infrastructure
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100