←back to thread

6 points standardresul | 2 comments | | HN request time: 0.545s | source

Hey HN,

I'm excited to share Label Backup, an open-source project I developed. This tool, written in Go, automates backups for databases running in your Docker containers using simple container labels. I built this with vibe coding.

How it Works:

- You add a few descriptive labels to your containers that run databases you want to back up (e.g., backup.enabled=true, backup.type=postgres, backup.cron="0 2 * * *", backup.conn=..., or backup.type=volume, backup.path=/my/data). - Label Backup, running as a separate container, automatically discovers these, then schedules and performs backups for: - PostgreSQL databases - MySQL databases - MongoDB databases - Redis data - Backups can be streamed to local storage or any S3-compatible service (such as AWS S3, MinIO, or Cloudflare R2). - Key features include on-the-fly Gzip compression, configurable retention policies, and webhook notifications for backup status.

My main goal was to build something lightweight, easy to configure, and reliable, aiming for a tool that (I hope!) feels smooth and intuitive to use.

You can find the source code, a detailed README, and a docker-compose.yml for a complete test environment on GitHub: https://github.com/resulgg/label-backup

The Docker Hub image is available at: resulgg/label-backup

I'd love to hear your thoughts and feedback.

Show context
vrighter ◴[] No.44012295[source]
no offense, but I would have to be a complete idiot to trust a vibe coded backup application.
replies(1): >>44013025 #
1. standardresul ◴[] No.44013025[source]
It’s currently running on my 40 GB database and hasn’t caused any issues so far. We shouldn’t be biased. I think this app should be mandatory for critical banking databases and databases that store government secrets.
replies(1): >>44019026 #
2. vrighter ◴[] No.44019026[source]
I used to work specifically on backup software. "Hasn't caused any problems so far" is not good enough.