gwc - provided configuration assumes postgresql hostname to be "database"

georchestra / geoserver_minimal_datadir

It is highly recommended to use this minimal data dir rather than letting geoserver create his own

0 stars 5 forks source link

gwc - provided configuration assumes postgresql hostname to be "database" #16

Open pmauduit opened 1 year ago

pmauduit commented 1 year ago

Introduced with https://github.com/georchestra/geoserver_minimal_datadir/pull/14, this leads to some questions which wheren't an issue when previously using h2 db:

shall we have a seperate branch considering docker (compose) vs non docker setups in this repository ?
In a kubernetes context, it won't probably be valid either
do we consider this repo as an example that has to be adapted anyway ?

fvanderbiest commented 1 year ago

We currently provide this datadir with 2 flavors (geofence / native security), for each major geOrchestra release. I think it would complicate things a lot if we were to take into account all deployment possibilities with branches. Instead, I think the deployment should take care of updating the provided files to their needs (eg geoserver running on docker does it here: https://github.com/georchestra/georchestra/blob/master/geoserver/webapp/src/docker/docker-entrypoint.d/00-geoserver-bootstrap

fvanderbiest commented 1 year ago

By default though, this repository should not assume we're running on docker but on a plain old "standard" install like the one we provide instructions for on https://github.com/georchestra/georchestra/blob/master/docs/setup.md. As a result, the provided GWC config should not use "database" as db host by default.

fvanderbiest commented 1 year ago

Good catch ! Thanks Pierre