-
Notifications
You must be signed in to change notification settings - Fork 363
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Undefined $S3_PREFIX results in nameless directory in s3 #59
Closed
Comments
Would you mind providing a PR for this? |
It would be also nice to have date as S3_PREFIX, for example value of "date --rfc-3339=date" output. |
blz-ea
added a commit
to blz-ea/dockerfiles
that referenced
this issue
Feb 4, 2020
- Bump alpine from 3.9 to 3.11 - Add Postgres v12 support (Fixes schickling#115) - Add multiple or all databases backup (Fixes schickling#10) - S3_PREFIX can be empty (Fixes schickling#59) - Add missing Documentation (Fixes schickling#87)
iloveitaly
pushed a commit
that referenced
this issue
Jan 21, 2022
Jblew
pushed a commit
to Jblew/postgres-backup-s3
that referenced
this issue
Feb 8, 2022
- Bump alpine from 3.9 to 3.11 - Add Postgres v12 support (Fixes schickling#115) - Add multiple or all databases backup (Fixes schickling#10) - S3_PREFIX can be empty (Fixes schickling#59) - Add missing Documentation (Fixes schickling#87)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
As per the title, by not setting
S3_PREFIX
I assumed all backups would go into the root of my dedicated backup bucket however the backup files end up under an unnamed directory when viewing the AWS S3 console.cat dump.sql.gz | aws s3 cp - s3://$S3_BUCKET/$S3_PREFIX/$(date +"%Y-%m-%dT%H:%M:%SZ").sql.gz || exit 2
I assume the extraneous
/
needs to be removed if$S3_PREFIX
isn't provided.The text was updated successfully, but these errors were encountered: