Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

docs: operations runbook (migrations, scaling, health, backups)

Open
#47 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
55/100
Issue type
Documentation
Clarity
Mostly clear
Activity status
Quiet
Tech stack
docker, java, kubernetes

Research direction

Start by locating the Quarkus health endpoint configuration and the database migration setup; the payload does not name specific files or tests. Check how state is persisted and how shutdown and restart are handled, then document migrations, backup and restore, supported replica topology, and health probes for Compose and Kubernetes. Done means self-hosters can follow the runbook for these operations.

Written by the indexing model from the issue text.

Description

documentation
Problem Statement

There is no operations runbook. Self-hosters need guidance on database migrations/backups, scaling stance (single vs multiple replicas), restart behavior (what survives a restart), and the health/readiness endpoints to wire into Docker/Kubernetes.

Proposed Solution

Add an operations guide covering: applying/rolling back DB migrations and backup/restore; the supported scaling topology and what is in-memory vs persisted; graceful-shutdown/restart behavior; and the SmallRye health endpoints (/q/health/live, /q/health/ready) with example Compose/Kubernetes probes.

Alternatives Considered
  • Scatter the information across the README — harder to find; a dedicated runbook serves operators better.
Priority

Nice to have

Code of Conduct
  • I have searched for existing issues and this is not a duplicate.
Dominant language
Java
Stars
35
Forks
7
Avg merge
9h 32m
Merged PRs (30d)
144

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from devops-thiago/ThrillhouseBot

All issues in devops-thiago/ThrillhouseBot

Similar issues

More Java issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.