From 6971edf4ca94a73cfc91b96de6e4108a24efc85d Mon Sep 17 00:00:00 2001 From: andryyy Date: Wed, 24 Oct 2018 19:11:05 +0200 Subject: [PATCH] Replace Apache by webserver --- docs/firststeps-rp.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/firststeps-rp.md b/docs/firststeps-rp.md index cf9c896b2..673bd0851 100644 --- a/docs/firststeps-rp.md +++ b/docs/firststeps-rp.md @@ -18,8 +18,8 @@ Recreate affected containers by running `docker-compose up -d`. !!! info 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. - On many servers logrotate will reload Apache2 daily anyway. + The downside of using mailcow as ACME client behind a reverse proxy is, that you will need to reload your webserver after acme-mailcow changed/renewed/created the certificate. You can either reload Apache daily or write a script to watch the file for changes. + On many servers logrotate will reload the webserver daily anyway. 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. @@ -158,4 +158,4 @@ postfix_c=$(docker ps -qaf name=postfix-mailcow) dovecot_c=$(docker ps -qaf name=dovecot-mailcow) nginx_c=$(docker ps -qaf name=nginx-mailcow) docker restart ${postfix_c} ${dovecot_c} ${nginx_c} -``` \ No newline at end of file +```