Message-ID: <3d2fd679-0cd6-3f1d-5048-4a644eb24001@cmatte.me>
Date: Mon, 8 Nov 2021 21:02:46 +0100
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101
 Thunderbird/91.3.0
To: PostgreSQL WWW <pgsql-www@lists.postgresql.org>
Content-Language: en-US
From: =?UTF-8?Q?C=c3=a9lestin_Matte?= <celestin.matte@cmatte.me>
Subject: Feature requests: some components still depend on postgresql.org
 deployment
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
Archived-At: 
 <https://www.postgresql.org/message-id/3d2fd679-0cd6-3f1d-5048-4a644eb24001%40cmatte.me>
Precedence: bulk

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