Re: Fill page when printing archived threads - Mailing list pgsql-www

From Magnus Hagander
Subject Re: Fill page when printing archived threads
Date
Msg-id CABUevExFUaz0htSuq3HaKxt-Ci7kTmVNHxQRvsP0Ys-+ZEh+Fw@mail.gmail.com
Whole thread Raw
In response to Re: Fill page when printing archived threads  (Paul A Jungwirth <pj@illuminatedcomputing.com>)
Responses Re: Fill page when printing archived threads
List pgsql-www
On Wed, 11 Feb 2026 at 23:32, Paul A Jungwirth <pj@illuminatedcomputing.com> wrote:
On Fri, Jan 23, 2026 at 2:17 AM Christoph Berg <cb@df7cb.de> wrote:
>
> Re: Paul A Jungwirth
> > I haven't tested with a locally-running copy of the site. Are there
> > instructions anywhere on setting that up? I'm comfortable with Django,
> > but I would still need a database, possibly a settings file, etc.
>
> docs/dev_install.rst is pretty good.

Thanks! My change is actually for the pgarchive repository, but I
think you're talking about the instructions for pgweb.

I did get pgweb running locally though. (It required some surprising
changes to requirements.txt, which I'll submit separately.) When I
click on the left nav's "Mailing Lists" link it goes to
http://localhost:8000/list/ which is a 404. So I guess postgresql.org
must be tying these together behind a reverse proxy. I still haven't
found any instructions for getting pgarchive running locally, but I'll
experiment a bit.

That's correct, the /list/ namespace is proxied.

The whole handling of templates between them is a mess (one has to remember to manually copy the base template between two different repos when changed), and we should really find a better way to handle that. But that is how it is now. 

FWIW, locally I just run pgarchive on a different listener and ignore that the link in the menu doesn't work and have a bookmark that point directly to it.b

--

pgsql-www by date:

Previous
From: Magnus Hagander
Date:
Subject: Re: Upgrade some pgweb python dependencies
Next
From: Paul A Jungwirth
Date:
Subject: Re: Fill page when printing archived threads