georchestra/gateway repository overview

⁠Quick reference

• Maintained by:
  georchestra.org⁠

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

⁠Featured tags

• latest, 2.0.x, 1.1.2
• latest-debug, 2.0.x-debug. It enables shell inside the container for debugging purposes.

⁠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/gateway

Gateway is a module for geOrchestra which offers

• OAuth2 and OpenID Connect authentication and authorization
• LDAP authentication and authorization
• HTTP/2
• Websockets

⁠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 gateway sub-directory.

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

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

⁠Where is it built

This image is built using maven : ./mvnw package -f gateway/ -Pdocker in repo folder.

Make can also be used : make docker.

⁠Running tests

Tests are run using maven : ./mvnw verify -pl :georchestra-gateway -ntp in repo folder.

Make can also be used : make test.

⁠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.