Nightly `pg_dump` backup workflow + restore runbook

[Miracle656]

Background

Wraith's data lives in a single managed Postgres. If it's lost or hits limits, re-indexing mainnet from scratch is slow. A nightly logical backup gives a minutes-not-days restore path. (This is the durability fallback for the mainnet deployment.)

What to build

A free scheduled GitHub Actions workflow that runs pg_dump and uploads the compressed dump to an artifact/release (or an object store), plus a short restore runbook.

Key files

• .github/workflows/db-backup.yml — new
• docs/backup-restore.md — new

Suggested execution

git checkout -b ci/nightly-pg-dump

1. Scheduled workflow (cron) using a DATABASE_URL secret
2. pg_dump --format=custom → gzip → upload as a dated artifact (retention ~14 days) or release asset
3. Document restore: pg_restore into a fresh Neon instance, then swap DATABASE_URL
4. Note per-network dumps (separate testnet/mainnet DBs)

Acceptance criteria

• Nightly job produces a downloadable dump
• Secrets used for connection (no creds in the repo)
• Restore runbook verified end-to-end once
• Handles both network DBs

Drips Wave · Complexity: Easy · 100 points

---

Required: Before submitting, join the contributor Telegram so your work can be tracked and counted toward the Stellar Wave: https://t.me/+fxHXq8f1SwlkZDBk

[notoflagosola-wq]

@notoflagosola-wq has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

Hi Maintener I’d love to resolve this issue. I’ve reviewed it, I’m ready to follow the guidelines and deliver a clean, tested solution. If you’re willing to assign it to me, I’d really appreciate the opportunity to prove myself.
‎Thank you for considering me!
‎
‎

ℹ️ Repo Maintainers: To accept this application, review their application or assign @notoflagosola-wq to this issue.

[DataRuth]

@DataRuth has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

Hello,

I am highly interested in tackling this issue. I have carefully reviewed the requirements and mapped out an efficient path forward for the implementation. Please assign the issue to me if it is still available, and I will get started immediately.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @DataRuth to this issue.

[tobiadewola41-eng]

@tobiadewola41-eng has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

I would like to work on this issue because

ℹ️ Repo Maintainers: To accept this application, review their application or assign @tobiadewola41-eng to this issue.

[Otfrugger]

@Otfrugger has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

I would like to apply for Issue #165 and implement a reliable nightly PostgreSQL backup and restore process for Wraith.

I will create a scheduled GitHub Actions workflow that securely uses the DATABASE_URL secret to run pg_dump, compress the resulting backup, and upload it as a dated artifact with an appropriate retention period. No database credentials will be committed to the repository.

I will also account for Wraith's separate testnet and mainnet databases, ensuring the workflow can produce backups for both networks without mixing their data.

Alongside the workflow, I will create docs/backup-restore.md with a clear recovery procedure covering how to obtain a backup, provision a fresh Neon PostgreSQL instance, restore it using pg_restore, verify the restored database, and safely update DATABASE_URL to point the application to the restored instance.

I will test the backup and restore process end-to-end at least once to ensure the documented procedure actually works in practice rather than only describing the expected commands.

My goal is to provide Wraith with a simple, automated, and secure recovery path that can turn a potential database failure from a lengthy re-indexing operation into a practical restore process.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Otfrugger to this issue.

[drips-wave]

Congratulations, @Otfrugger! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on August 31, 2026.

🧑‍💻 @Otfrugger: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.

Warning

When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.

🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.

🌊 Happy Wave 🌊