Closed ImreSamu closed 2 years ago
14-master
; but the test failed .. so reverted.The init file is not generated from templates? I took a quick look and don't see it being generated, but I could swear it was generated in the past 🤔
I just wonder if there's a way to avoid all this duplication...
Now we have
jq
based templating; as in our upstream repo ( https://github.com/docker-library/postgres/blob/master/apply-templates.sh )With the jq
templating we can adapt some complex templating logic like this example:
--with-libxslt \
--with-icu \
{{ if .major >= 11 then ( -}}
--with-llvm \
{{ ) else "" end -}}
{{ if .major >= 14 then ( -}}
--with-lz4 \
{{ ) else "" end -}}
But some quick improvements could be made now ; like renaming the other template files ;
/initdb-postgis.sh
----> /initdb-postgis.sh.template
/update-postgis.sh
----> /update-postgis.sh.template
I have updated the *-master images
the 14-master
version:
PostgreSQL 14.2 (Debian 14.2-1.pgdg110+1) on x86_64-pc-linux-gnu, compiled by gcc (Debian 10.2.1-6) 10.2.1 20210110, 64-bit
POSTGIS="3.3.0dev 3.2.0-809-gc9885d527" [EXTENSION] PGSQL="140" GEOS="3.11.0dev-CAPI-1.16.0" PROJ="9.1.0" LIBXML="2.9.10" LIBJSON="0.15" LIBPROTOBUF="1.3.3" WAGYU="0.5.0 (Internal)"
CI/CD tests OK: :heavy_check_mark:
Ready to merge. ( cc @phillipross )
the https://github.com/postgis/docker-postgis/pull/290 only has been fixed the template files; and this PR with
make update
- regenerating everywhere.( cc: @strk ; @phillipross )
Locally tested:
the new
postgis/postgis:13-3.2-alpine
version:the new
postgis/postgis:13-3.2
version:and the server logs look ok. Alpine log
debian log - has an extra
You are now connected to database "postgres" as user "postgres".