-
Notifications
You must be signed in to change notification settings - Fork 285
Add support for restore mode #491
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
base: master
Are you sure you want to change the base?
Conversation
Is this something that can be done via GUI or is there CLI work needed? If there is operational work required, the write mount can be overridden when a restore is needed. This is a bit more safety but a bit more uncomfortable. |
The admin needs to provide the restorable backups in the |
This is right, but it would not work with scenarios like Portainer based deployments, as it requires modification of the yaml file. |
This PR has been automatically marked as stale because it has not had recent activity. |
env: | ||
VERSION: 'develop' # TODO: revert before merging! |
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.
TODO: revert before merging
Zammad 7.0 will feature restoring backups in docker. This happens inside the
zammad-backup
container, which therefore needs to mount thezammad-storage
volume inrw
mode rather thanro
so that files can actually be restored.Breaking Change
This change of the mount point must be transferred to any local docker-compose.yml definitions that are already deployed and need to be updated.