Alternative location for vmail

maverick

Hi all,

I’m deploying a new mailcow server and we have a separate disk for email data.
Looking at the documentation, I see that in regard of moving vmail volume seems to be two ways, an “old” way and a “new” way. However it seems the article is more aimed at existing installations rather than new installations.

https://mailcow.github.io/mailcow-dockerized-docs/u_e-dovecot-vmail-volume/

So my question is, for a new installation, should I go for that “new way” proposed on doc, or opt for the “old” way and add a docker-compose.override?

Thank you.

diekuh

Hi, I’d go with the new way. 🙂

maverick

Don’t mind me asking why is the “new way” better than the “old way” - in the means that, why is creating symbolic links to a new location a better method than having an override config file with the correct configuration? I’m having a hard time grasping this concept.

edit: and btw, so should I create the symbolic link BEFORE or AFTER running docker compose and deploying mailcow?

diekuh

Before.

There is no “better”. I think it is just more hassle-free.