| From: | Paul A Jungwirth <pj(at)illuminatedcomputing(dot)com> |
|---|---|
| To: | Christoph Berg <cb(at)df7cb(dot)de>, Paul A Jungwirth <pj(at)illuminatedcomputing(dot)com>, pgsql-www(at)postgresql(dot)org |
| Subject: | Re: Fill page when printing archived threads |
| Date: | 2026-02-11 22:32:40 |
| Message-ID: | CA+renyWA77wVu2Zis3=tdBWAj-Xbz7cKuZbMbo6=o5cMR7wZVQ@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-www |
On Fri, Jan 23, 2026 at 2:17 AM Christoph Berg <cb(at)df7cb(dot)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.
Yours,
--
Paul ~{:-)
pj(at)illuminatedcomputing(dot)com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Paul A Jungwirth | 2026-02-11 22:39:50 | Upgrade some pgweb python dependencies |
| Previous Message | Greg Sabino Mullane | 2026-02-09 18:34:50 | Re: Incorrect description for "SET" abbreviation in Time Zone Appendix |