From: | Célestin Matte <celestin(dot)matte(at)cmatte(dot)me> |
---|---|
To: | PostgreSQL WWW <pgsql-www(at)lists(dot)postgresql(dot)org> |
Subject: | Feature requests: some components still depend on postgresql.org deployment |
Date: | 2021-11-08 20:02:46 |
Message-ID: | 3d2fd679-0cd6-3f1d-5048-4a644eb24001@cmatte.me |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-www |
Hello,
As I've finished installing pglister and its components, it appears that part of them still make it difficult to install a non-postgresql.org instance. I'm thinking of two issues:
- Pgweb's auth is a part of pgweb, an application running most of postgresql.org's website. I would be great if that component could be separated from pgweb, so that users can deploy it easily, without having to maintain the whole repository.
If other software providing the same auth function already exist and could be used instead of pgweb, feel free to point them to me.
- In the different repositories, some files contain links and elements related to postgresql.org:
* home.html (pglister): main page with instructions for postgresql.org
* base.html (pgweb, pgarchives): headers, navigation bar
* index.html (pgweb, pgarchives): main page, contains news etc.
* page.html (pgarchives): quick links for navigation
* context.py (pgweb): site navigation structure
It would be great to find a solution to make these files configurable for a new deployment.
Cheers,
--
Célestin Matte
From | Date | Subject | |
---|---|---|---|
Next Message | Timothy Chadwick | 2021-11-08 21:59:31 | psycopg2 article editor access |
Previous Message | Célestin Matte | 2021-11-08 20:01:55 | [PATCHES] pglister: Add README.md and INSTALL.md |