The version published at this time contains only non-breaking changes.
- ATS for Data Specification on Mineral Resources
- ATS for Data Specification on Energy Resources
- ATS for Data Specification on Oceanographic geographical features
- ATS for Data Specification on Atmospheric Conditions and Meteorological Geographical Features
- ATS for Data Specification on Statistical Units
- ATS for Data Specification on Soil
- ETS for Data Specification on Mineral Resources
- ETS for Data Specification on Energy Resources
- ETS for Data Specification on Oceanographic geographical features
- ETS for Data Specification on Atmospheric Conditions and Meteorological Geographical Features
- ETS for Data Specification on Statistical Units
- ETS for Data Specification on Soil
- #440 Fixed prefixes on lu-gml - #647
- #458 Polygon, PolyhedralSurface and TriangulatedSurface added to bu-as b.5 and lc-v-as a.1 - #633
- #473 Added certificates in validation process - #648
- #526 hb-as.a.4 paths fixed - #649
- #532 Parsed 'lang' to String to avoid type error - #650
- #555 ef-as a.1 conditions fixed for empty observations - #651
- #566 Fixed "An error has occurred" error on new UI.
- #571 Fixed SwaggerUI documentation.
- #572 Added missing ';' to media-type test & Update URL to point against atom URL - #653
- #576 Added missing semicolons to WFS - #652
- #582 Added missing '.Default' layers - #654
- #587 Updated wrong variable - #655
- #601 noDateTypeForSpecification message typo fixed - #657
The section containing the deployment process using Docker image and troubleshooting section. You can also find these in the training materal
docker run --name inspire-validator -d -p 8090:8090 -v ~/etf:/etf ghcr.io/inspire-mif/helpdesk-validator/inspire-validator:2021.3 #Launches a container with the image, exposing it port 8090 through the same port in the host machine, and uses a volume in the local file system, on the directory ~/etf
Modifying the Docker image
In the inspire-validator ZIP file you can find all the resources needed to generate the Docker image from this release. If you would like to tweak anything from it, you can modify any of its contents (Dockerfile, entrypoint file, configuration files... ), then execute the command
docker build -t [IMAGE_NAME]:[VERSION]
You can run this again using the run command
docker run --name inspire-validator -d -p 8080:8080 -v ~/etf:/etf [IMAGE_NAME]:[VERSION]
Deployment on the production host
The Docker image is set up to run at localhost to be deployed on any machine. However, users may need to acces their validator on a dedicated host, usually with a domain name. For proper functioning of the validator, their UI and correct rendering of Test Reports, validator needs to be configured to run on a domain.
If you want to run the webapp in another host, you can change the configuration file, inside the .war file inside the inspire-validator zip file accompanying this release, at
WEB-INF/classes/etf-config.properties, and modify the
etf.webapp.base.url property. Then you can proceed to the build process described in the previous point.
Exposing the validator through a proxy
Usually host machines are connected in a private network that access to the Internet through a proxy. The Docker client needs to be configured to make use of this proxy, in order to be able to build the image and set up running the container.
For the build process, you need to add the following arguments to the command
--build-arg http_proxy=[HTTP_PROXY_URL:PORT] --build-arg https_proxy=[HTTPS_PROXY_URL:PORT] --build-arg no_proxy=127.0.0.1,localhost,*.<my-domain>
For the run command, you need to add the environment variables to it
--env http_proxy=[HTTP_PROXY_URL:PORT] --env https_proxy=[HTTPS_PROXY_URL:PORT] --env no_proxy=127.0.0.1,localhost,*.<mydomain>
These can also be set up in the Dockerfile, using the keyword ENV
For more information please check out https://docs.docker.com/network/proxy
For further configuration, please download the file inspire-validator-2021.3.zip and follow the instructions in the README.md file inside the .zip file.
Find changelog details & deployment instructions:
Assets contained in this release: