emacs-bug-tracker
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[debbugs-tracker] bug#30459: closed (Certbot service patches)


From: GNU bug Tracking System
Subject: [debbugs-tracker] bug#30459: closed (Certbot service patches)
Date: Sat, 03 Mar 2018 21:54:01 +0000

Your message dated Sat, 03 Mar 2018 22:52:57 +0100
with message-id <address@hidden>
and subject line Re: [bug#30459] [PATCH 06/11] services: certbot: Get certbot 
to run non-interactively.
has caused the debbugs.gnu.org bug report #30459,
regarding Certbot service patches
to be marked as done.

(If you believe you have received this mail in error, please contact
address@hidden)


-- 
30459: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=30459
GNU Bug Tracking System
Contact address@hidden with problems
--- Begin Message --- Subject: Certbot service patches Date: Wed, 14 Feb 2018 22:33:19 +0100 User-agent: mu4e 1.0; emacs 25.3.1
Hi,

Here are a few patches that aim to improve the Certbot service.

One problem I have is that reconfiguring takes a bit too much time if
there are many certificates.  I wonder if there is a way to avoid
running 'certbot-activation' when the configuration didn't change.

Also, I had not reproducible networking issues while updating the
certificates, but they may be related to my deploy hooks and have
nothing to do with the service.

Comments welcome :-)

Clément



--- End Message ---
--- Begin Message --- Subject: Re: [bug#30459] [PATCH 06/11] services: certbot: Get certbot to run non-interactively. Date: Sat, 03 Mar 2018 22:52:57 +0100 User-agent: Gnus/5.13 (Gnus v5.13) Emacs/25.3 (gnu/linux)
Clément Lassieur <address@hidden> skribis:

> I pushed the series as is in the master branch, because it changes the
> API and it's better that the potential users use the new API as soon as
> possible.  (And it works anyway.)  I'll add a patch implementing the
> certbot-activation as a Shepherd service.

Awesome.

Remember to close the bug by emailing address@hidden as I’m
doing here.  :-)

Ludo’.


--- End Message ---

reply via email to

[Prev in Thread] Current Thread [Next in Thread]