opensanctions / opensanctions/poliloom
Add Meilisearch index to automated GCS backup
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 22
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
Description
Currently PostgreSQL is backed up daily to GCS via poliloom-backup.timer, but Meilisearch is only backed up manually via Makefile targets (index-dump, index-snapshot) to local dumps/ directory.
Task
Add Meilisearch dump to the automated backup pipeline so it's also uploaded to GCS.
Options
- Extend
poliloom-backup.serviceto also dump Meilisearch - Create separate
poliloom-backup-index.service/timer
Reference
- Existing backup:
systemd-timers/poliloom-backup.service - Meilisearch dump logic:
Makefile(index-dumptarget)
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 systemd-timers/poliloom-backup.service and the Makefile's index-dump target to compare the existing PostgreSQL backup flow with the Meilisearch dump logic. Check the related timer configuration and verify the resulting dump is uploaded to GCS by the automated backup, with the chosen service or timer completing successfully.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- google-cloud
- Domain
- cloud, infrastructure, search
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100