From: Tobias Geerinckx-Rice <me@tobias.gr>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: Pierre Neidhardt <mail@ambrevar.xyz>, 32845@debbugs.gnu.org
Subject: bug#32845: guix.info: Missing manual
Date: Fri, 28 Sep 2018 22:39:21 +0200 [thread overview]
Message-ID: <87a7o1nypy.fsf@tobias.gr> (raw)
In-Reply-To: <87h8i91jaq.fsf@gnu.org>
Ludo', Guix,
Ludovic Courtès wrote:
> Ricardo Wurmus <rekado@elephly.net> skribis:
>> “certbot” can be used with manual DNS validation, which
>> requires us to deploy a DNS TXT record. This can be automated
>> with
>> certbot hooks (scripts that have access to the token that
>> should be
>> published via environment variables) or through JSON mode,
>> which returns
>> an object with the token that can be processed through other
>> means.
>
> I didn’t know about all this! Looks like our Certbot service
> doesn’t
> support it though?
Not out of the box, and last time I checked vanilla certbot didn't
provide an nsupdate (RFC2136) hook alongside all the DNSaaS API
rubbish.
But it's certainly possible, and wonderfully stable once set
up. t.gr runs entirely on GuixSD + Knot + DNS-validated LE certs.
Kind regards,
T G-R
next prev parent reply other threads:[~2018-09-28 20:40 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-26 10:33 bug#32845: guix.info: Missing manual Pierre Neidhardt
2018-09-26 18:01 ` Ricardo Wurmus
2018-09-26 19:44 ` Pierre Neidhardt
2018-09-26 20:10 ` Ricardo Wurmus
2018-09-27 13:46 ` Ludovic Courtès
2018-09-27 15:28 ` Ricardo Wurmus
2018-09-27 17:37 ` Pierre Neidhardt
2018-09-28 20:08 ` Ludovic Courtès
2018-09-28 20:03 ` Ludovic Courtès
2018-09-28 20:38 ` Ricardo Wurmus
2018-09-28 20:39 ` Tobias Geerinckx-Rice [this message]
2018-09-29 16:14 ` Ludovic Courtès
2020-01-25 18:00 ` sirgazil via Bug reports for GNU Guix
2020-01-28 10:28 ` Ludovic Courtès
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87a7o1nypy.fsf@tobias.gr \
--to=me@tobias.gr \
--cc=32845@debbugs.gnu.org \
--cc=ludo@gnu.org \
--cc=mail@ambrevar.xyz \
/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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).