summaryrefslogtreecommitdiffstats
path: root/dovecot/dovecot.conf
diff options
context:
space:
mode:
authorMalfurious <m@lfurio.us>2024-06-08 14:55:47 -0400
committerMalfurious <m@lfurio.us>2024-06-09 14:16:42 -0400
commitf70fb0720d2a643905ba8263253b16b973f6bc36 (patch)
tree27c057db3858b8d4f0c3c730dab905fd4b1efb0e /dovecot/dovecot.conf
parent26dab860bd733e4f110fc837e1f3d8c682248502 (diff)
downloadmailnode-f70fb0720d2a643905ba8263253b16b973f6bc36.tar.gz
mailnode-f70fb0720d2a643905ba8263253b16b973f6bc36.zip
Create docker image and services
As hinted by the previous commit, the mailnode system is built in a single docker image for simplicity. Defining multiple Dockerfiles would lead to many redundant tasks and be harder to maintain. So a common image for all services is built. However, the compose file spawns a unique container for each service, and communication occurs via the filesystem, through volumes. Note also that some fields in docker-compose.yml are required to be set by the end-user. The mail system is oriented around virtual users, so that nobody needs their own unix system account. However, best security practice is to create a dedicated user to own the mails - this user shouldn't be used for any other purpose. For this, the Dockerfile creates the user "vmailbox". The reason for declaring port exposure for TCP/80 is to enable automated TLS encryption with nginx-proxy-acme. This port is not actually opened by the compose file. Signed-off-by: Malfurious <m@lfurio.us>
Diffstat (limited to '')
0 files changed, 0 insertions, 0 deletions