IMGIITRoorkee / IMGIITRoorkee/chakra-docker
Database is backed up weekly, giving a seven-day RPO for a metadata-sized database
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 1
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
PostgreSQL is dumped **weekly**, with no WAL archiving and no replica — so a disk failure on Sunday morning loses a week of page metadata, permissions, subdomain configs and short URLs.
The database holds only metadata (content lives on disk), so the dump is small and `pg_dump -Fc` takes seconds. There is no performance argument for weekly.
**Fix:** change the cron to hourly. A one-character change for a 168× RPO improvement.
---
**Evidence**
```
ARCHITECTURE.md:373 (schedule is server-side crontab)
```
- Verified against: `origin/master 44ca47e (2026-07-25)`
- Verdict: **CONFIRMED**
Contributor guide
No contributing guide indexed for this repository
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 ARCHITECTURE.md:373 to confirm that the backup schedule is defined in the server-side crontab and inspect the current PostgreSQL dump entry. Change the schedule from weekly to hourly, then verify that the dump remains a pg_dump -Fc backup and that the resulting schedule provides the intended recovery-point objective.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- postgresql
- Domain
- databases, devops
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 68/100