Skip to content

Commit 07ecec5

Browse files
committed
Add why use MySQL-BKUP
1 parent bc4aab6 commit 07ecec5

File tree

1 file changed

+48
-15
lines changed

1 file changed

+48
-15
lines changed

README.md

Lines changed: 48 additions & 15 deletions
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@
33
**MYSQL-BKUP** is a Docker container image designed to **backup, restore, and migrate MySQL databases**.
44
It supports a variety of storage options and ensures data security through GPG encryption.
55

6-
**MYSQL-BKUP** is designed for seamless deployment on **Docker** and **Kubernetes**, simplifying MySQL backup, restoration, and migration across environments.
6+
MYSQL-BKUP is designed for seamless deployment on **Docker** and **Kubernetes**, simplifying MySQL backup, restoration, and migration across environments.
77
It is a lightweight, multi-architecture solution compatible with **Docker**, **Docker Swarm**, **Kubernetes**, and other container orchestration platforms.
88

99

@@ -69,12 +69,6 @@ MYSQL-BKUP has been tested and runs successfully on:
6969

7070
- [PostgreSQL](https://github.com/jkaninda/pg-bkup)
7171

72-
## Storage:
73-
- Local
74-
- AWS S3 or any S3 Alternatives for Object Storage
75-
- SSH remote storage server
76-
- FTP remote storage server
77-
- Azure Blob storage
7872

7973
## Quickstart
8074

@@ -204,10 +198,7 @@ spec:
204198
# Pin the image tag to a specific release version in production.
205199
# See available releases: https://github.com/jkaninda/mysql-bkup/releases
206200
image: jkaninda/mysql-bkup
207-
command:
208-
- /bin/sh
209-
- -c
210-
- backup -d dbname
201+
command: ["backup", "-d", "dbname"]
211202
resources:
212203
limits:
213204
memory: "128Mi"
@@ -248,10 +239,7 @@ spec:
248239
containers:
249240
- name: pg-bkup
250241
image: jkaninda/mysql-bkup
251-
command:
252-
- /bin/sh
253-
- -c
254-
- backup -d dbname
242+
command: ["backup", "-d", "dbname"]
255243
env:
256244
- name: DB_HOST
257245
value: "mysql"
@@ -270,6 +258,51 @@ spec:
270258
restartPolicy: OnFailure
271259
```
272260

261+
---
262+
263+
## 🚀 Why Use MYSQL-BKUP?
264+
265+
**MYSQL-BKUP** isn't just another MySQL backup tool, it's a robust, production-ready solution purpose-built for modern DevOps workflows.
266+
267+
Here’s why developers, sysadmins, and DevOps choose **MYSQL-BKUP**:
268+
269+
### ✅ All-in-One Backup, Restore & Migration
270+
271+
Whether you're backing up a single database, restoring critical data, or migrating across environments, MYSQL-BKUP handles it all with a **single, unified CLI** no scripting gymnastics required.
272+
273+
274+
### 🔄 Works Everywhere You Deploy
275+
276+
Designed to be cloud-native:
277+
278+
* **Runs seamlessly on Docker, Docker Swarm, and Kubernetes**
279+
* Supports **CronJobs** for automated scheduled backups
280+
* Compatible with GitOps and CI/CD workflows
281+
282+
### ☁️ Flexible Storage Integrations
283+
284+
Store your backups **anywhere**:
285+
286+
* Local disks
287+
* Amazon S3, MinIO, Wasabi, Azure Blob, FTP, SSH
288+
289+
### 🔒 Enterprise-Grade Security
290+
291+
* **GPG Encryption**: Protect sensitive data with optional encryption before storing backups locally or in the cloud.
292+
* **Secure Storage** Options: Supports S3, Azure Blob, SFTP, and SSH with encrypted transfers, keeping backups safe from unauthorized access.
293+
294+
### 📬 Instant Notifications
295+
296+
Stay in the loop with real-time notifications via **Telegram** and **Email**. Know immediately when a backup succeeds—or fails.
297+
298+
### 🏃‍♂️ Lightweight and Fast
299+
300+
Written in **Go**, MYSQL-BKUP is fast, multi-arch compatible (`amd64`, `arm64`, `arm/v7`), and optimized for minimal memory and CPU usage. Ideal for both cloud and edge deployments.
301+
302+
### 🧪 Tested. Verified. Trusted.
303+
304+
Actively maintained with **automated testing**, **Docker image size optimizations**, and verified support across major container platforms.
305+
273306
---
274307
## Available image registries
275308

0 commit comments

Comments
 (0)