From a428dc789abb41a1a473f9fd6cc005cf1b9090dc Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Andr=C3=A9?= Date: Tue, 16 Oct 2018 12:22:53 +0200 Subject: [PATCH] Change RP info --- docs/firststeps-rp.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/docs/firststeps-rp.md b/docs/firststeps-rp.md index d00c39b6c..cf9c896b2 100644 --- a/docs/firststeps-rp.md +++ b/docs/firststeps-rp.md @@ -19,8 +19,9 @@ 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. - 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.