From: Marius Bakke <marius@gnu.org>
To: "Ludovic Courtès" <ludo@gnu.org>,
"Christopher Baines" <mail@cbaines.net>
Cc: Daniela Lura <danielaluraa@gmail.com>, guix-devel@gnu.org
Subject: Re: [Guix Website] A Search Page for Packages
Date: Tue, 14 Jul 2020 21:47:15 +0200 [thread overview]
Message-ID: <87pn8xc20s.fsf@gnu.org> (raw)
In-Reply-To: <87zh82kz5y.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 518 bytes --]
Ludovic Courtès <ludo@gnu.org> writes:
> On berlin we’ll have to keep using nginx I guess (there’s too much
> config in there), but perhaps Varnish is an option for the Data Service.
To be clear, Varnish is not a replacement for nginx (it does not even
speak HTTPS), the typical deployment is nginx -> Varnish -> backend. It
introduces another "hop" though.
I'm not sure if it's worth the added complexity here, just thought I'd
mention it. It's a programming language for caching/proxying logic.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]
next prev parent reply other threads:[~2020-07-14 19:47 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-08 18:49 [Guix Website] A Search Page for Packages Daniela Lura
2020-07-08 20:31 ` Cook, Malcolm
2020-07-08 21:00 ` pelzflorian (Florian Pelz)
2020-07-10 10:15 ` Daniela Lura
2020-07-09 0:53 ` Bengt Richter
2020-07-09 6:17 ` Pierre Neidhardt
2020-07-10 10:26 ` Daniela Lura
2020-07-09 7:47 ` Hartmut Goebel
2020-07-09 8:50 ` zimoun
2020-07-09 9:32 ` YP
2020-07-13 13:56 ` Ludovic Courtès
2020-07-13 14:00 ` Ludovic Courtès
2020-07-13 20:10 ` Christopher Baines
2020-07-13 22:04 ` Marius Bakke
2020-07-14 13:24 ` Ludovic Courtès
2020-07-14 19:47 ` Marius Bakke [this message]
2020-09-06 14:19 ` Daniela Lura
2020-09-07 10:20 ` Ludovic Courtès
2020-09-08 16:50 ` Daniela Lura
2020-09-08 16:38 ` Hartmut Goebel
2020-07-14 9:19 ` Daniela Lura
2020-07-14 13:23 ` Ludovic Courtès
-- strict thread matches above, loose matches on Subject: below --
2022-11-05 16:53 Luis Felipe
2022-11-05 18:53 ` Christopher Baines
2022-11-05 19:59 ` Luis Felipe
2022-11-09 16:43 ` Luis Felipe
2022-11-13 8:46 ` Christopher Baines
2022-11-15 13:30 ` Luis Felipe
2022-11-16 16:25 ` Christopher Baines
2022-11-16 18:46 ` Luis Felipe
2022-11-16 14:55 ` Luis Felipe
2022-11-16 16:32 ` Christopher Baines
2022-11-16 18:50 ` Luis Felipe
2022-11-18 19:03 ` Luis Felipe
2022-11-19 10:51 ` Christopher Baines
2022-11-19 12:03 ` Luis Felipe
2022-11-19 13:53 ` Luis Felipe
2022-11-21 11:06 ` Ludovic Courtès
2022-11-19 16:07 ` John Kehayias
2022-11-19 16:13 ` Christopher Baines
2022-11-21 20:30 ` John Kehayias
2022-11-20 22:33 ` zimoun
2022-11-21 8:57 ` Christopher Baines
2022-11-21 17:03 ` zimoun
2022-11-22 8:23 ` Christopher Baines
2022-11-21 12:57 ` Ludovic Courtès
2022-11-21 13:21 ` Christopher Baines
2022-11-21 19:11 ` Luis Felipe
2022-11-21 19:00 ` Luis Felipe
2022-11-21 20:42 ` Julien Lepiller
2022-11-07 9:18 ` 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=87pn8xc20s.fsf@gnu.org \
--to=marius@gnu.org \
--cc=danielaluraa@gmail.com \
--cc=guix-devel@gnu.org \
--cc=ludo@gnu.org \
--cc=mail@cbaines.net \
/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).