Closed Matchlighter closed 5 years ago
As I understand the python code and the bash script, I think this is good. When can we merge?
@Matchlighter do we need to wait for the https://github.com/hardware/mailserver/pull/336 PR to be merge before we merge this one?
Yeah, this one is based on #336 - so merging this one would automatically merge #336.
On May 29, 2019, 11:22 AM, at 11:22 AM, Istvan Szabo notifications@github.com wrote:
@Matchlighter do we need to wait for the https://github.com/hardware/mailserver/pull/336 PR to be merge before we merge this one?
-- You are receiving this because you were mentioned. Reply to this email directly or view it on GitHub: https://github.com/hardware/mailserver/pull/366#issuecomment-497030933
Awesome. Then can we merge these PRs?
I'm down. I don't have merge perms though.
@Matchlighter looks like I have the power to do it. Should we merge this or we should merge the other PR first?
@sknight80 Semantically, I'd probably recommend merging #336 first. This one does completely include it, but merging the other first will make sure that it has a merge-commit in the Git history.
@Matchlighter, I am going to merge this PR as well.
Well, I use traefik v2 wildcard acme.json, and it always show [INFO] Live Certificates match
and ignore the new certs. docker restart
not works, you have to run docker stop
then docker start
to the service, another workaround is delete /ssl
directory in container before updating the acme.json file. This issue really confuse me. Hope helps!
Description
(Built on top of https://github.com/hardware/mailserver/pull/336)
Adds FS watches on Traefik's
acme.json
file and on a mounted Let's Encryptlive
directory. Automatically reparses the cert files and reloads Postfix and Dovecot.Watcher is debounced to 3 seconds and compares the old and new
privkey.pem
before reloading Postfix and Dovecot.Mount locations for
acme.json
andlive
were kept the same. Moveddump.log
to<mount>/mail/ssl/acme_dump.log
.Risks
Type of change
Status
How has this been tested ?
touch
ing theacme.json
file from outside the container and validating expectations