MIME-Version: 1.0
References: <3d2fd679-0cd6-3f1d-5048-4a644eb24001@cmatte.me>
In-Reply-To: <3d2fd679-0cd6-3f1d-5048-4a644eb24001@cmatte.me>
From: Magnus Hagander <magnus@hagander.net>
Date: Wed, 10 Nov 2021 12:58:27 +0100
Message-ID: 
 <CABUevExy3uCmseaa5O=_NQ_deo6vbzX9e0inqWFA_ifuBjyybg@mail.gmail.com>
Subject: Re: Feature requests: some components still depend on postgresql.org
 deployment
To: =?UTF-8?Q?C=C3=A9lestin_Matte?= <celestin.matte@cmatte.me>
Cc: PostgreSQL WWW <pgsql-www@lists.postgresql.org>
Content-Type: multipart/alternative; boundary="00000000000062584105d06df229"
Archived-At: 
 <https://www.postgresql.org/message-id/CABUevExy3uCmseaa5O%3D_NQ_deo6vbzX9e0inqWFA_ifuBjyybg%40mail.gmail.com>
Precedence: bulk

--00000000000062584105d06df229
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Mon, Nov 8, 2021 at 9:02 PM C=C3=A9lestin Matte <celestin.matte@cmatte.m=
e>
wrote:

> 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 coul=
d
> be used instead of pgweb, feel free to point them to me.
>

For a standalone installation of pglister, it should be possible to just
use the django authentication system (or any other plugin for that). If you
just set USE_PG_COMMUNITY_AUTH=3DFalse.  If there are things missing in a
setup like that, I think that's should be fixed, rather than cementing the
connection with pgweb.


- 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.
>

Per above, I don't think pgweb should be part of this, as that has never
been intended to be used outside of www.postgresql.org, and I don't think
it should be.

For the other two, pglister and pgarchives, yes, being able to do that
makes a lot of sense.

I wonder if we can get away with doing something as simple as the
pgeu-system "skin directory" setup. Basically, for those you can configure
a SYSTEM_SKIN_DIRECTORY. This directory will get it's templtes directory
inserted in the path *ahead* of anything that's in the main system, and
also a code/ directory added to the python path, and has some separate
settings etc. There's an example of a skin at
https://github.com/pgeu/pgeu-web for example (ignore the part that's
template.jinja, just the template, code and media directories are relevant.

It would still inherit dependencies like bootstrap unless one overrides
*all* templates (but for pgarchives and pglister that might actually be
reasonable to do, as there aren't that many). But definitely being able to
replace things like the "overall theme" should be fairly simple that way?

--=20
 Magnus Hagander
 Me: https://www.hagander.net/ <http://www.hagander.net/>
 Work: https://www.redpill-linpro.com/ <http://www.redpill-linpro.com/>

--00000000000062584105d06df229
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr">On Mon, Nov 8, 2021 at 9:02 PM C=C3=A9les=
tin Matte &lt;<a href=3D"mailto:celestin.matte@cmatte.me">celestin.matte@cm=
atte.me</a>&gt; wrote:<br></div><div class=3D"gmail_quote"><blockquote clas=
s=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid r=
gb(204,204,204);padding-left:1ex">Hello,<br>
<br>
As I&#39;ve finished installing pglister and its components, it appears tha=
t part of them still make it difficult to install a <a href=3D"http://non-p=
ostgresql.org" rel=3D"noreferrer" target=3D"_blank">non-postgresql.org</a> =
instance. I&#39;m thinking of two issues:<br>
<br>
- Pgweb&#39;s auth is a part of pgweb, an application running most of <a hr=
ef=3D"http://postgresql.org" rel=3D"noreferrer" target=3D"_blank">postgresq=
l.org</a>&#39;s website. I would be great if that component could be separa=
ted from pgweb, so that users can deploy it easily, without having to maint=
ain the whole repository.<br>
If other software providing the same auth function already exist and could =
be used instead of pgweb, feel free to point them to me.<br></blockquote><d=
iv><br></div><div>For a standalone installation of pglister, it should be p=
ossible to just use the django authentication system (or any other plugin f=
or that). If you just set USE_PG_COMMUNITY_AUTH=3DFalse.=C2=A0 If there are=
 things missing in a setup like that, I think that&#39;s should be fixed, r=
ather than cementing the connection with pgweb.</div><div><br></div><div><b=
r></div><div><br></div><blockquote class=3D"gmail_quote" style=3D"margin:0p=
x 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
- In the different repositories, some files contain links and elements rela=
ted to <a href=3D"http://postgresql.org" rel=3D"noreferrer" target=3D"_blan=
k">postgresql.org</a>:<br>
* home.html (pglister): main page with instructions for <a href=3D"http://p=
ostgresql.org" rel=3D"noreferrer" target=3D"_blank">postgresql.org</a><br>
* base.html (pgweb, pgarchives): headers, navigation bar<br>
* index.html (pgweb, pgarchives): main page, contains news etc.<br>
* page.html (pgarchives): quick links for navigation<br>
* context.py (pgweb): site navigation structure<br>
<br>
It would be great to find a solution to make these files configurable for a=
 new deployment.<br></blockquote><div><br></div><div>Per above, I don&#39;t=
 think pgweb should be part of this, as that has never been intended to be =
used outside of <a href=3D"http://www.postgresql.org">www.postgresql.org</a=
>, and I don&#39;t think it should be.</div><div><br></div><div>For the oth=
er two, pglister and pgarchives, yes, being able to do that makes a lot of =
sense.</div><div><br></div><div>I wonder if we can get away with doing some=
thing as simple as the pgeu-system &quot;skin directory&quot; setup. Basica=
lly, for those you can configure a SYSTEM_SKIN_DIRECTORY. This directory wi=
ll get it&#39;s templtes directory inserted in the path *ahead* of anything=
 that&#39;s in the main system, and also a code/ directory added to the pyt=
hon path, and has some separate settings etc. There&#39;s an example of a s=
kin at=C2=A0<a href=3D"https://github.com/pgeu/pgeu-web">https://github.com=
/pgeu/pgeu-web</a> for example (ignore the part that&#39;s template.jinja, =
just the template, code and media directories are relevant.</div><div><br><=
/div><div>It would still inherit dependencies like bootstrap unless one ove=
rrides *all* templates (but for pgarchives and pglister that might actually=
 be reasonable to do, as there aren&#39;t that many). But definitely being =
able to replace things like the &quot;overall theme&quot; should be fairly =
simple that way?</div><div><br></div></div>-- <br><div dir=3D"ltr" class=3D=
"gmail_signature"><div dir=3D"ltr"><div>=C2=A0Magnus Hagander<br>=C2=A0Me: =
<a href=3D"http://www.hagander.net/" target=3D"_blank">https://www.hagander=
.net/</a><br>=C2=A0Work: <a href=3D"http://www.redpill-linpro.com/" target=
=3D"_blank">https://www.redpill-linpro.com/</a></div></div></div></div>

--00000000000062584105d06df229--