From 038ec5942edce74e9f9e69533c6de985e775c6ba Mon Sep 17 00:00:00 2001 From: Thomas VIAL Date: Wed, 11 Sep 2019 16:49:25 +0200 Subject: [PATCH] Updated FAQ and Tips (markdown) --- docs/content/config/troubleshooting/faq.md | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/docs/content/config/troubleshooting/faq.md b/docs/content/config/troubleshooting/faq.md index 137cf939..1d476b47 100644 --- a/docs/content/config/troubleshooting/faq.md +++ b/docs/content/config/troubleshooting/faq.md @@ -25,14 +25,16 @@ You should use a [data volume container](https://medium.com/@ramangupta/why-dock Assuming that you use `docker-compose` and a data volume container named `maildata`, you can backup your user mails like this: -```docker run --rm -ti \ +``` +docker run --rm -ti \ -v maildata:/var/mail \ -v mailstate:/var/mail-state \ -v /backup/mail:/backup \ alpine:3.2 \ tar cvzf /backup/mail-`date +%y%m%d-%H%M%S`.tgz /var/mail /var/mail-state -find /backup/mail -type f -mtime +30 -exec rm -f {} \;``` +find /backup/mail -type f -mtime +30 -exec rm -f {} \; +``` ### What about `mail-state` folder? This folder consolidates all data generated by the server itself to persist when you upgrade.