Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1n8n1i-0000V0-I4 for pgsql-www@arkaria.postgresql.org; Sat, 15 Jan 2022 17:39:42 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1n8n1A-0001bP-3J for pgsql-www@arkaria.postgresql.org; Sat, 15 Jan 2022 17:39:08 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1n8n19-0001aG-SH for pgsql-www@lists.postgresql.org; Sat, 15 Jan 2022 17:39:07 +0000 Received: from mail-lf1-x133.google.com ([2a00:1450:4864:20::133]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1n8n17-00030t-Id for pgsql-www@lists.postgresql.org; Sat, 15 Jan 2022 17:39:06 +0000 Received: by mail-lf1-x133.google.com with SMTP id m3so27278227lfu.0 for ; Sat, 15 Jan 2022 09:39:05 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hagander-net.20210112.gappssmtp.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=Brf2cUP21V3T1SPi+7an1BgpmMF/gRpT4rqv+a7CkfA=; b=JhqNSf+pm0ncNGRcKu0joIL4A9CGBC4P0UjzcEdl2kJgPcBowugeXBk82lyTubcYqn x/fn0BTRh1WwI6DIix896RlqG5ZbW2WUvz0luZnzDGqe87GoXYOK19xb68mRsReSlApt oNddKhSKkodfrwVhN1Ju2wFtySbIaPQo9G2EhEqAhUJIvvrAeLZe37lFS0wInOthrr+6 6/5IEpkUpUNFzgma92IZmH3fj9KJYQTAQtK/fEOJQkgiKwrEQ2McCTUmBkWhMulY2E49 nOTljbHCX1aE65PX5kdnwEC7dicwfwR20w7uUze67G3k1soDIWnl1W9rCyyk1yRj8N91 lTgw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=Brf2cUP21V3T1SPi+7an1BgpmMF/gRpT4rqv+a7CkfA=; b=BskWjtM7gajNO+7zuHjICQ3E4pS9KR55471o3N4sjJTF7re7JUFQbD/+HyQGW8l8o1 175vJMw8p1V6ucaujWTndSex2UbQd8hikM8Cz4P09eXbeEO4TfSpqhzYV0CLRmjBr4bZ ntu0pPDZ7+90AJWzMmKplTey+g9XKdl24YXH1dDBdbSzrFfmIteazc0O2eK1J1UkHQal vzIRUHSmwRqqtJiFpxq5UaFCJvPHaESgch7vLCv0CuSGcGoUZcWI24LetFIoNu8cOOeH ZZUjnpcl7fNsIevZHeUe5iShl/BXmPOweHjBW/XRoPPAtmspVresyfUrvey5WPpPPqQa 9i0w== X-Gm-Message-State: AOAM530ZbNhdbypSYGSFobnzG5flxYkilpjsa3uhoJqP/d6Z9vunOnZG L1Viraq/UnJRIWhHVz02QaUTPCRYBNAorGlh4EY6PihNIkA= X-Google-Smtp-Source: ABdhPJzOh8A+ApHLkfPY5C3d4b2Vd2N/k2bZy+PFFpcZtxpsfaA7+zGhOoIxYyZVCZgEqMVyRONK34WC9gDFwfyiH/Q= X-Received: by 2002:a05:6512:3191:: with SMTP id i17mr11132734lfe.496.1642268344094; Sat, 15 Jan 2022 09:39:04 -0800 (PST) MIME-Version: 1.0 References: <6945e6fc-0006-454e-079f-f7b91af2be22@cmatte.me> In-Reply-To: From: Magnus Hagander Date: Sat, 15 Jan 2022 18:38:52 +0100 Message-ID: Subject: Re: [PATCH] pgweb: Add ARCHIVES_FRONT_ADDRESS to allow configuration of archives To: =?UTF-8?Q?C=C3=A9lestin_Matte?= Cc: pgsql-www@lists.postgresql.org Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On Wed, Oct 27, 2021 at 11:45 AM C=C3=A9lestin Matte wrote: > > > This patch adds a new parameter ARCHIVES_FRONT_ADDRESS, which is then n= ever used. Instead it passes in ARCHIVES_SEARCH_SERVER into the templates. > > > > I'm pretty sure that's not intentional? They should both b ARCHIVES_FRO= NT_ADDRESS? > > Oops, indeed, this is the product of a failed git merge --squash. > > Fixed patch attached. Finally cycling back to this one, sorry about the long delay. This does look much better, applied with th modification that it should take the whole URL and not just the hostname -- which maks it work better in development for example. --=20 Magnus Hagander Me: https://www.hagander.net/ Work: https://www.redpill-linpro.com/