-
Notifications
You must be signed in to change notification settings - Fork 19
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
feat(s3): add s3 support for backup storage #70
Conversation
Signed-off-by: Valentin Maillot <[email protected]>
Co-authored-by: Lucas Bickel <[email protected]>
Signed-off-by: Valentin Maillot <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Did you consider doing it in two containers as doxed here? The RH way might make for a more optional mc
cli experience in case we want this image to keep a low footprint in existing installs.
LGTM
oh wow, nop, not even considered that. Shall I go that way? That would be fine for me. Then we would not have to care about modifying the script anyway. |
Signed-off-by: Valentin Maillot <[email protected]>
i'll go this way for now, let's see if we want to improve that in the future! |
* feat(s3): add s3 support for backup storage * feat(Dockerfile): use mc RPM instead of binary directly * feat(backup.sh): use mcli instead of mc * chore(README): add link to MinIO object expiration configuration doc Signed-off-by: Valentin Maillot <[email protected]> --------- Signed-off-by: Valentin Maillot <[email protected]> Co-authored-by: Lucas Bickel <[email protected]>
https://zammad.adfinis.com/#ticket/zoom/27839