self-hosted/Mailu
1
0
Fork 0
mirror of https://github.com/Mailu/Mailu.git synced 2025-08-10 22:31:47 +02:00
Code Issues Releases Activity

Update mount path to mailu/certs

Browse Source 
- Thus, we write to /data/mailu/certs, since LE uses the same location
- The dumper created cert.pem and key.pem
- Mount /data/mailu/certs to certs, where nginx picks them up
This commit is contained in:
Dennis Boldt
2019-08-11 01:12:34 +02:00
committed by GitHub
parent a9089710c8
commit 841ce96fbf
1 changed files with 4 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
docs/reverse.rst
View File

@@ -179,17 +179,17 @@ One such example is ``mailu/traefik-certdumper``, which has been adapted for use
# Folder, which contains the acme.json # Folder, which contains the acme.json
- "/data/traefik:/traefik" - "/data/traefik:/traefik"
# Folder, where your.doma.in.crt and your.doma.in.key will be written # Folder, where your.doma.in.crt and your.doma.in.key will be written
- "/data/traefik/certs:/output" - "/data/mailu/certs:/output"
Assuming you have ``volume-mounted`` your ``acme.json`` put to ``/data/traefik`` on your host. The dumper will then write out ``/data/traefik/certs/cert.pem`` and ``/data/traefik/certs/key.pem`` whenever ``acme.json`` is updated. Assuming you have ``volume-mounted`` your ``acme.json`` put to ``/data/traefik`` on your host. The dumper will then write out ``/data/mailu/certs/cert.pem`` and ``/data/mailu/certs/key.pem`` whenever ``acme.json`` is updated.
Yay! Now let’s mount this to our ``front`` container like: Yay! Now let’s mount this to our ``front`` container like:
.. code-block:: yaml .. code-block:: yaml
volumes: volumes:
- /data/traefik/certs/$TRAEFIK_DOMAIN.crt:/certs/cert.pem - /data/mailu/certs:/certs
- /data/traefik/certs/$TRAEFIK_DOMAIN.key:/certs/key.pem - /data/mailu/certs:/certs
This works, because we set ``TLS_FLAVOR=mail``, which picks up the key-certificate pair (e.g., ``cert.pem`` and ``key.pem``) from the certs folder in the root path (``/certs/``). This works, because we set ``TLS_FLAVOR=mail``, which picks up the key-certificate pair (e.g., ``cert.pem`` and ``key.pem``) from the certs folder in the root path (``/certs/``).