docker support for geoserver datadir checker

[jeanmi151]

I see path of geoserver datadir is static in several ways
I am getting the error :

gaia-back-1  | ERROR:Utils:/srv/data/geoserver/global.xml not found, dunno where to find geoserver datadir

https://github.com/georchestra/gaia/blob/master/gsdscanner/__init__.py#L28

also i think it don't use tomcat backend but jetty !
https://github.com/georchestra/gaia/blob/master/geordash/utils.py#L59C38-L59C44

[landryb]

yeah, i've already said up-front i didnt know how it'd work with jetty, nor how to find the path of the geoserver datadir in a docker environment, this is more or less expected that some code needs to be written for that (not by me)

two distinct things are needed:

• where to find the datadir
• how to list the available jndi resources made available to geoserver

[jeanmi151]

in docker env it is stored in /mnt/geoserver_datadir (usually), not sure how to detect it as this path is coming from java ARGs (-DGEOSERVER_DATA_DIR https://github.com/georchestra/geoserver/blob/main/webapp/src/docker/Dockerfile#L41 )

jndi resources are in the jetty-env.xml (geOr datadir https://github.com/georchestra/datadir/blob/docker-master/geoserver/jetty-env.xml )

I guess we should think about a way to custom this path without changing the source code (even for classic install, everybody wouldn't have the datadir in /srv).

[landryb]

in docker env it is stored in /mnt/geoserver_datadir (usually), not sure how to detect it as this path is coming from java ARGs (-DGEOSERVER_DATA_DIR https://github.com/georchestra/geoserver/blob/main/webapp/src/docker/Dockerfile#L41 )

there's already code that looks for -DGEOSERVER_DATA_DIR in https://github.com/georchestra/gaia/blob/master/geordash/utils.py#L101, might want to improve that

jndi resources are in the jetty-env.xml (geOr datadir https://github.com/georchestra/datadir/blob/docker-master/geoserver/jetty-env.xml )

then some code needs to be written to:

• find that jetty-env.xml file path from the running environment like done for tomcat
• parse the resources from the xml like done for tomcat

I guess we should think about a way to custom this path without changing the source code (even for classic install, everybody wouldn't have the datadir in /srv).

there has to be a fallback at some point if all the previous heuristics for lookup failed, i made the decision to default to the ansible defaults.

[jeanmi151]

part of this pr is solved,
still need to address the JNDI part