From: "Clément Lassieur" <clement@lassieur.org>
To: Tobias Alexandra Platen <guix@platen-software.de>
Cc: guix-devel@gnu.org
Subject: Re: How to get nginx and letsencrypt working on the guix system
Date: Tue, 31 Oct 2023 20:51:47 +0100 [thread overview]
Message-ID: <87y1fi7ep8.fsf@lassieur.org> (raw)
In-Reply-To: <67713d793edf4bcdcbf897dcfa3b657191c610b3.camel@platen-software.de> (Tobias Alexandra Platen's message of "Tue, 31 Oct 2023 19:23:32 +0100")
On Tue, Oct 31 2023, Tobias Alexandra Platen wrote:
> I installed the guix system on a virtual machine, and changed the
> config as documented in the guix manual under 12.9.19 Web Services:
>
> (service certbot-service-type
> (certbot-configuration
> (email "tplaten@posteo.de")
> (certificates (list (certificate-
> configuration
> (domains '("stream.isengaara.de")) (deploy-hook
> %nginx-deploy-hook))))))
> ;;; nginx testing
> (service nginx-service-type
> (nginx-configuration
> (server-blocks
> (list (nginx-server-configuration
> (server-name '("stream.isengaara.de"))
> (root "/srv/http/stream.isengaara.de"))))))
>
> Certbot needs running nginx to create a certificate, and nginx wont
> start without a certificate. The documentation does not explain how
> to solve this circular service dependency.
Hi! There is some reading about it there:
https://debbugs.gnu.org/cgi/pkgreport.cgi?include=subject%3Acertbot;package=guix
There is a proposal from Brice but it's not implemented yet, as far as I
know (https://debbugs.gnu.org/cgi/bugreport.cgi?bug=46961).
Please talk about it on the bug tracker rather than guix devel, this
allows for better tracking.
Thanks,
Clément
prev parent reply other threads:[~2023-10-31 19:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-31 18:23 How to get nginx and letsencrypt working on the guix system Tobias Alexandra Platen
2023-10-31 18:27 ` Julien Lepiller
2023-10-31 19:00 ` Tobias Alexandra Platen
2023-10-31 19:51 ` Clément Lassieur [this message]
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=87y1fi7ep8.fsf@lassieur.org \
--to=clement@lassieur.org \
--cc=guix-devel@gnu.org \
--cc=guix@platen-software.de \
/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.