From: Phil <phil@beadling.co.uk>
To: Tobias Geerinckx-Rice <me@tobias.gr>
Cc: help-guix@gnu.org
Subject: Re: Running Substitute Server over https
Date: Sat, 06 Feb 2021 12:32:02 +0000 [thread overview]
Message-ID: <85mtwhe5rx.fsf@beadling.co.uk> (raw)
In-Reply-To: <874kipxyc8.fsf@nckx>
> That's all ‘guix publish’ does; it doesn't speak HTTPS.
Ahh ot-it, so I just need to stick it behind a reverse proxy - thanks
for clarifying.
next prev parent reply other threads:[~2021-02-06 12:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-06 10:18 Running Substitute Server over https Phil
2021-02-06 10:52 ` Tobias Geerinckx-Rice
2021-02-06 12:32 ` Phil [this message]
2021-02-06 10:58 ` Edouard Klein
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=85mtwhe5rx.fsf@beadling.co.uk \
--to=phil@beadling.co.uk \
--cc=help-guix@gnu.org \
--cc=me@tobias.gr \
/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.
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).