Re: Containerized development environment for pgweb - Mailing list pgsql-www

From Magnus Hagander
Subject Re: Containerized development environment for pgweb
Date
Msg-id CABUevExeAnK57iVPDdRfapRgVsWs7iv9zsGXJitby84OgybjjQ@mail.gmail.com
Whole thread Raw
In response to Re: Containerized development environment for pgweb  (Yogesh Sharma <yogesh.sharma@catprosystems.com>)
Responses Re: Containerized development environment for pgweb  (Yogesh Sharma <yogesh.sharma@catprosystems.com>)
List pgsql-www


On Thu, Jun 27, 2024 at 2:25 PM Yogesh Sharma <yogesh.sharma@catprosystems.com> wrote:
On 6/26/24 04:23, Magnus Hagander wrote:
> On Wed, Jun 26, 2024 at 10:07 AM Justin Clift <justin@postgresql.org>
> wrote:
>
>     On 2024-06-21 23:08, Yogesh Sharma wrote:
>     <snip>
>     > docker-compose.yml - to create proper dependency between python and
>     > postgres container
>
>     This one's using PG 16:
>
>        image: postgres:16
>
>     Does anyone know if the PG infrastructure uses PG 16 too?
>
>     Asking because it'd make sense for them to match, just in case. :)
>
>
> It also is on python 3.7 which should be 3.9 to match what's deployed.
> In general, I'd recommend starting off the debian bullseye container
> instead of the python specific one -- that's what's used in the
> production deployments, so it makes sense to keep to the same.
> That way it could also be using the same versions of the debian
> packages for all requirements (basically everything except Django
> itself), to ensure it's exactly the same.
>
> //Magnus

Which Debian release is used by PG infrastructure?

Currently, bullseye. 

--

pgsql-www by date:

Previous
From: Yogesh Sharma
Date:
Subject: Re: Containerized development environment for pgweb
Next
From: Akshat Jaimini
Date:
Subject: Doubt regarding Postgres Documentation on FTP Server from v17 onward