georchestra/geoserver repository overview

⁠Quick reference

• Maintained by:
  georchestra.org⁠

• Where to get help:
  the geOrchestra Github repo⁠, IRC chat⁠, Stack Overflow

⁠Featured tags

• latest, 2.28.2-georchestra
• 25.0.x
• 24.0.x
• geofence, 2.28.2-georchestra-geofence,
• 25.0.x-geofence
• 24.0.x-geofence

⁠Quick reference

• Where to file issues:
  https://github.com/georchestra/georchestra/issues⁠

• Supported architectures:
  amd64⁠

• Source of this description:
  docs repo's directory⁠

⁠What is georchestra/geoserver

Geoserver is a module for geOrchestra which offers

• a Map and Feature server compliant with OGC standards (WMS, WFS, WCS, WPS, CSW, ...)

geOrchestra's Geoserver is a fork of GeoServer⁠.

⁠How to use this image

As for every other geOrchestra webapp, its configuration resides in the data directory (datadir⁠), typically something like /etc/georchestra, where it expects to find a geoserver sub-directory.

It is recommended to use the official docker composition: https://github.com/georchestra/docker⁠.

For this specific component, see the section geoserver in the georchestra/docker/docker-compose.yml⁠ file.

⁠Where is it built

This image is built using maven : ./mvnw -Pdocker package docker:build in georchestra⁠ repo.

⁠License

View license information⁠ for the software contained in this image.

As with all Docker images, these likely also contain other software which may be under other licenses (such as Bash, etc from the base distribution, along with any direct or indirect dependencies of the primary software being contained).

As for any docker image, it is the user's responsibility to ensure that usages of this image comply with any relevant licenses for all software contained within.