-
Notifications
You must be signed in to change notification settings - Fork 229
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
Closes: #379 - Add mount point for /opt/zammad/storage #380
Conversation
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.
Apart from my one concern the rest is looking good to me.
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.
Looking good.
If we are upgrading from 5.3 where the docker-compose file has already created and we use the new docker-compose that uses Will this cause us to lose any data, if we don't add zammad-data back to the compose file? |
If you find that data is missing, you can temporarily re-add the previous mount point, and move the data to the new location. |
Thanks for the answer. I gave it a try without re-adding it. It looks like all our data is still there. |
) * Closes: zammad#379 - Add mount point for /opt/zammad/storage * Remove zammad-storage from nginx container again.
It will not hurt to have this mount point, even if it is not used by default. Instead, it will make maintenance easier.