| From: | Magnus Hagander <magnus(at)hagander(dot)net> |
|---|---|
| To: | Justin Clift <justin(at)postgresql(dot)org> |
| Cc: | Yogesh Sharma <yogesh(dot)sharma(at)catprosystems(dot)com>, PostgreSQL WWW Mailing List <pgsql-www(at)postgresql(dot)org> |
| Subject: | Re: Containerized development environment for pgweb |
| Date: | 2024-06-26 08:23:28 |
| Message-ID: | CABUevExinP613imuwnyoddy05Z7qAvkMe9s+454YmsDVLzL4rQ@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-www |
On Wed, Jun 26, 2024 at 10:07 AM Justin Clift <justin(at)postgresql(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Justin Clift | 2024-06-26 11:36:06 | Re: Containerized development environment for pgweb |
| Previous Message | Dave Page | 2024-06-26 08:11:55 | Re: Containerized development environment for pgweb |