search

nickbreen / docker-mysql-backup-cron

GNU General Public License v2.0
6 stars 9 forks source link

backup.sh and restore.sh are not consistent about S3 bucket name #5

Closed clescot closed 8 years ago

clescot commented 8 years ago

Hi, /backup.sh works like a charm. but when i want to list available backups via the /restore.sh command, an error occurs : 

ERROR: Bucket 's3:' does not exist
ERROR: S3 error: 404 (NoSuchBucket): The specified bucket does not exist

according to this line https://github.com/nickbreen/docker-mysql-backup-cron/blob/master/restore.sh#L14 , BUCKET should not start with 's3://' prefix, but this is required by the backup.sh command. When i remove from the BUCKET variable the s3:// prefix, it lists available backups successfully, but further backups fail. best regards, Charles.

nickbreen commented 8 years ago

Ah yes. I switched between the prefix and without. I'll update the restore script, feel free to fork and send a PR if you urgently need it. On 19/02/2016 11:23 am, "charles lescot" notifications@github.com wrote:

Hi, /backup.sh works like a charm. but when i want to list available backups via the /restore.sh command, an error occurs :

ERROR: Bucket 's3:' does not exist ERROR: S3 error: 404 (NoSuchBucket): The specified bucket does not exist

according to this line https://github.com/nickbreen/docker-mysql-backup-cron/blob/master/restore.sh#L14 , BUCKET should not start with 's3://' prefix, but this is required by the backup.sh command. When i remove from the BUCKET variable the s3:// prefix, it lists available backups successfully, but further backups fail. best regards, Charles.

— Reply to this email directly or view it on GitHub https://github.com/nickbreen/docker-mysql-backup-cron/issues/5.