Originally created by @MichaelKunze on GitHub (May 23, 2016).
Hello there!
I have the following setup:
10 different certificates for nginx vhosts
1 cert for incoming mail server
1 cert for outgoing mail server
What i want to archive is to restart nginx only once when any of the 10 vhost certificates have been renewed. I'm already using the hooks that are present in the example directory but that function would be called for each certificate (so 10 times in worse case) which would mean 10 nginx restarts within a single letsencrypt.sh run.
Is there any existing feature i can use to reach my goal?
Thanks in advance,
Michael
Originally created by @MichaelKunze on GitHub (May 23, 2016).
Hello there!
I have the following setup:
- 10 different certificates for nginx vhosts
- 1 cert for incoming mail server
- 1 cert for outgoing mail server
What i want to archive is to restart nginx only once when any of the 10 vhost certificates have been renewed. I'm already using the hooks that are present in the example directory but that function would be called for each certificate (so 10 times in worse case) which would mean 10 nginx restarts within a single letsencrypt.sh run.
Is there any existing feature i can use to reach my goal?
Thanks in advance,
Michael
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @MichaelKunze on GitHub (May 23, 2016).
Hello there!
I have the following setup:
What i want to archive is to restart nginx only once when any of the 10 vhost certificates have been renewed. I'm already using the hooks that are present in the example directory but that function would be called for each certificate (so 10 times in worse case) which would mean 10 nginx restarts within a single letsencrypt.sh run.
Is there any existing feature i can use to reach my goal?
Thanks in advance,
Michael
@Rayne commented on GitHub (May 23, 2016):
Side note: You could also reload the configuration instead of restarting the webserver.
@lukas2511 commented on GitHub (May 24, 2016):
This is planned, see discussion for #148