all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Carlo Zancanaro <carlo@zancanaro.id.au>
To: Christine Lemmer-Webber <cwebber@dustycloud.org>
Cc: 50872@debbugs.gnu.org
Subject: bug#50872: Prosody service + letsencrypt certs improvements
Date: Thu, 30 Sep 2021 07:06:31 +1000	[thread overview]
Message-ID: <87zgrv13hp.fsf@zancanaro.id.au> (raw)
In-Reply-To: <87h7e4tyb3.fsf@dustycloud.org>

Hi Christine,

On Tue, Sep 28 2021, Christine Lemmer-Webber wrote:
> Hm, in other words we really ought to run this attached to some 
> hook related to the letsencrypt services... when they renew 
> successfully, it should trigger this command, I'd think.  We do 
> similar things for nginx, etc...

I'm pretty sure Guix doesn't do anything automatic when 
certificates are renewed. For nginx there's an example in the 
manual for how to set up a deploy hook to reload the 
certificates[1], so I expect that you'll have to set up something 
similar.

My prosody setup has this deploy hook:

    (program-file
     "reload-certificates"
     #~(let ((prosodyctl (string-append #$(specification->package 
     "prosody")
                                        "/bin/prosodyctl")))
         (system* prosodyctl "--root" "cert" "import" 
         "/etc/letsencrypt/live")
         (system* prosodyctl "reload")))

but I have recently had some trouble with it (prosody hasn't been 
reloading the certificate properly). I don't think my issue is 
related to this deploy hook, though.

I hope that helps!

Carlo

[1]: 
https://guix.gnu.org/en/manual/en/html_node/Certificate-Services.html




  reply	other threads:[~2021-09-29 21:23 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-28 17:01 bug#50872: Prosody service + letsencrypt certs improvements Christine Lemmer-Webber
2021-09-29 21:06 ` Carlo Zancanaro [this message]
2021-09-29 23:43   ` Christine Lemmer-Webber

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87zgrv13hp.fsf@zancanaro.id.au \
    --to=carlo@zancanaro.id.au \
    --cc=50872@debbugs.gnu.org \
    --cc=cwebber@dustycloud.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.