Emilien Devos

Reopening because the third step is not done yet.

Docker compose v2 should work, it's the version 1 that won't work anymore. I did add a notice about that in the README: https://github.com/georchestra/docker#quick-start

Details of the docker images provided by @f-necas  

For georchestra 24.0 I would really like to migrate all the containers to non-root containers for security reasons. As this is a new release, it can be a good thing...

If the application support TLS1.3 then only `-Dhttps.protocols=TLSv1.2,TLSv1.3` should be used.

The point here is to have built-in support for two major functionalities. The first one being to support the ability to easily override the current files in the container from...

I have been thinking of backporting these changes to previous georchestra docker images. As it won't affect the usability/functionalities of the actual components of georchestra.

Additional containers to do in medium priority: - [x] smtp - [x] database - [x] analytics - [x] import/datafeeder-ui - [x] datafeeder - [x] ogc-api-records - [ ] gateway

merged in master, backport PRs: - https://github.com/georchestra/georchestra/pull/4106 - https://github.com/georchestra/georchestra-cas-server/pull/19 - datafeeder ui-frontend, no idea?? seems to be making a tag with release - https://github.com/georchestra/mapstore2-georchestra/pull/676 - https://github.com/georchestra/mapstore2-georchestra/pull/675 - docker-exim - smtp,...

geOrchestra 23.0.4 was released with the custom scripts support: - georchestra/analytics:23.0.4 - georchestra/cas:23.0.4-georchestra - georchestra/console:23.0.4 - georchestra/datafeeder:23.0.4 - georchestra/datafeeder-frontend:23.0.4 - georchestra/gn-cloud-ogc-api-records-service:23.0.4 - georchestra/geoserver:23.0.4 - georchestra/header:23.0.4 - georchestra/mapstore:23.0.4-georchestra - georchestra/ldap:23.0.4 -...