Browse Source
Fixed SCHEDULE EV description (#147)
PR #136 switched from go-cron to crond, so it doesn't support seconds and formats like '@daily' anymore
pull/154/head
Denis
2 years ago
committed by
GitHub
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with
1 additions and
7 deletions
-
mysql-backup-s3/README.md
|
|
@ -26,10 +26,4 @@ $ docker run -e S3_ACCESS_KEY_ID=key -e S3_SECRET_ACCESS_KEY=secret -e S3_BUCKET |
|
|
- `S3_ENSURE_BUCKET_EXISTS` set to `no` to assume the bucket exists, avoiding the need of S3 read permissions (default: yes) |
|
|
- `S3_ENSURE_BUCKET_EXISTS` set to `no` to assume the bucket exists, avoiding the need of S3 read permissions (default: yes) |
|
|
- `S3_S3V4` set to `yes` to enable AWS Signature Version 4, required for [minio](https://minio.io) servers (default: no) |
|
|
- `S3_S3V4` set to `yes` to enable AWS Signature Version 4, required for [minio](https://minio.io) servers (default: no) |
|
|
- `MULTI_FILES` Allow to have one file per database if set `yes` default: no) |
|
|
- `MULTI_FILES` Allow to have one file per database if set `yes` default: no) |
|
|
- `SCHEDULE` backup schedule time, see explainatons below |
|
|
|
|
|
|
|
|
|
|
|
### Automatic Periodic Backups |
|
|
|
|
|
|
|
|
|
|
|
You can additionally set the `SCHEDULE` environment variable like `-e SCHEDULE="@daily"` to run the backup automatically. |
|
|
|
|
|
|
|
|
|
|
|
More information about the scheduling can be found [here](http://godoc.org/github.com/robfig/cron#hdr-Predefined_schedules). |
|
|
|
|
|
|
|
|
- `SCHEDULE` backup schedule time in [cron format](https://crontab.guru) like `7 2,14 * * *` |
