nickslowinski/mailcow-dockerized-docs
1
0
Fork 0
Code Issues Pull-Requests Projekte Releases Pakete Wiki Aktivität

Change RP info

Quellcode durchsuchen
Dieser Commit ist enthalten in:
André 2018-10-16 12:22:53 +02:00
Ursprung 751650b51c
Commit a428dc789a
1 geänderte Dateien mit 2 neuen und 1 gelöschten Zeilen
Statistiken anzeigen Patch-Datei herunterladen Diff-Datei herunterladen Alle Dateien ausklappen Alle Dateien einklappen

3
docs/firststeps-rp.md
Datei anzeigen

@ -19,8 +19,9 @@ Recreate affected containers by running `docker-compose up -d`.
!!! info !!! info
Using the site configs below will **forward ACME requests to mailcow** and let it handle certificates itself. Using the site configs below will **forward ACME requests to mailcow** and let it handle certificates itself.
The downside of using mailcow as ACME client behind a reverse proxy is, that you will need to reload Apache after the certificate changed. You can either reload Apache daily or write a script to watch the file for changes. The downside of using mailcow as ACME client behind a reverse proxy is, that you will need to reload Apache after the certificate changed. You can either reload Apache daily or write a script to watch the file for changes.
On many servers logrotate will reload Apache2 daily anyway.
If you want to use a local certbot installation, you can omit the configurations for port 80 and change the SSL certificate parameters accordingly. If you want to use a local certbot installation, you will need to change the SSL certificate parameters accordingly.
**Make sure you run a post-hook script** when you decide to use external ACME clients. You will find an example at the bottom of this page. **Make sure you run a post-hook script** when you decide to use external ACME clients. You will find an example at the bottom of this page.