georchestra/datafeeder-frontend repository overview

⁠Quick reference

• Maintained by:
  georchestra.org⁠

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

⁠Featured tags

• latest, 1.0.x
• Old versions number 24.0.x

⁠Quick reference

• Where to file issues:

  • https://github.com/georchestra/georchestra/issues⁠

• Supported architectures:
  amd64⁠

• Source of this description:
  repo datafeeder-ui/ directory⁠

⁠What is georchestra/datafeeder-frontend

Datafeeder-frontend is geOrchestra's frontend UI service provides the wizard-like user interface to interact with the backend⁠, it aims to upload file based datasets and publish them to GeoServer and GeoNetwork in one shot.

Datafeeder-frontend was a fork of geonetwork-ui/datafeeder⁠ Angular app.

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

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

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

⁠Where is it built

This image is built using maven : ../mvnw clean package docker:build -Pdocker in datafeeder-ui⁠ 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.