scottk/Mailu
1
0
Fork 0
mirror of https://github.com/optim-enterprises-bv/Mailu.git synced 2025-11-03 19:47:52 +00:00
Code Issues Packages Projects Releases Wiki Activity

POD_ADDRESS need to be defined for admin service (dovecot authentification) fixes #694

Browse Source 
- updated the docs
- corrected a typo
This commit is contained in:
ofthesun9
2018-10-31 14:27:37 +00:00
parent 1a5e106bb8
commit 5067b5c59a
2 changed files with 6 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
docs/swarm/master/README.md
View File

@@ -30,7 +30,7 @@ mzrm9nbdggsfz4sgq6dhs5i6n flying-dutchman Ready Active
### Volume definition ### Volume definition
For data persistance (the Mailu services might be launched/relaunched on any of the swarm nodes), we need to have Mailu data stored in a manner accessible by every manager or worker in the swarm. For data persistance (the Mailu services might be launched/relaunched on any of the swarm nodes), we need to have Mailu data stored in a manner accessible by every manager or worker in the swarm.
Hereafter we will assume that "Mailu Data" is available on every node at "$ROOT/certs:/certs" (GlusterFS and nfs shares have been successfully used). Hereafter we will assume that "Mailu Data" is available on every node at "$ROOT" (GlusterFS and nfs shares have been successfully used).
On this example, we are using: On this example, we are using:
- the mesh routing mode (default mode). With this mode, each service is given a virtual IP adress and docker manages the routing between this virtual IP and the container(s) providing this service. - the mesh routing mode (default mode). With this mode, each service is given a virtual IP adress and docker manages the routing between this virtual IP and the container(s) providing this service.
@@ -77,7 +77,7 @@ Instead, we will use the following work-around:
We need also to: We need also to:
- add a deploy section for every service - add a deploy section for every service
- modify the way the ports are defined for the front service - modify the way the ports are defined for the front service
- add the POD_ADDRESS_RANGE definition for imap, smtp and antispam services - add the POD_ADDRESS_RANGE definition for admin (for imap), smtp and antispam services
## Docker compose ## Docker compose
An example of docker-compose-stack.yml file is available here: An example of docker-compose-stack.yml file is available here:
@@ -128,8 +128,6 @@ services:
image: mailu/dovecot:$VERSION image: mailu/dovecot:$VERSION
restart: always restart: always
env_file: .env env_file: .env
environment:
- POD_ADDRESS_RANGE=10.0.1.0/24
volumes: volumes:
- "$ROOT/mail:/mail" - "$ROOT/mail:/mail"
- "$ROOT/overrides:/overrides" - "$ROOT/overrides:/overrides"
@@ -188,6 +186,8 @@ services:
image: mailu/admin:$VERSION image: mailu/admin:$VERSION
restart: always restart: always
env_file: .env env_file: .env
environment:
- POD_ADDRESS_RANGE=10.0.1.0/24
volumes: volumes:
- "$ROOT/data:/data" - "$ROOT/data:/data"
- "$ROOT/dkim:/dkim" - "$ROOT/dkim:/dkim"

4
docs/swarm/master/README_nfs_example.md
View File

@@ -157,8 +157,6 @@ services:
image: mailu/dovecot:$VERSION image: mailu/dovecot:$VERSION
restart: always restart: always
env_file: .env env_file: .env
environment:
- POD_ADDRESS_RANGE=10.0.1.0/24
volumes: volumes:
# - "$ROOT/mail:/mail" # - "$ROOT/mail:/mail"
- type: volume - type: volume
@@ -241,6 +239,8 @@ services:
image: mailu/admin:$VERSION image: mailu/admin:$VERSION
restart: always restart: always
env_file: .env env_file: .env
environment:
- POD_ADDRESS_RANGE=10.0.1.0/24
volumes: volumes:
# - "$ROOT/data:/data" # - "$ROOT/data:/data"
- type: volume - type: volume