georchestra/security-proxy
Security-proxy module for the geOrchestra SDI
10K+
Maintained by:
georchestra.org
Where to get help:
the geOrchestra Github repo, IRC chat, Stack Overflow
latest
, 24.0.x
, 23.1.x
Where to file issues:
https://github.com/georchestra/georchestra/issues
Supported architectures:amd64
Source of this description:
docs repo's security-proxy/
directory
georchestra/security-proxy
Security-proxy belongs to geOrchestra core, since it is the component which :
Security-proxy is deprecated in favor of Gateway. It is still maintained for now, but will be removed in future versions.
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 analytics sub-directory.
It is recommended to use the official docker composition: https://github.com/georchestra/docker.
For this specific component, see the section proxy
in the georchestra/docker/docker-compose.yml
file.
This image is built using maven : ../mvnw package docker:build -Pdocker
in georchestra
repo security-proxy/
folder.
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.
docker pull georchestra/security-proxy