Releases · INSPIRE-MIF/helpdesk-validator

25 Sep 16:44

v2024.3

7e40160

v2024.3 - 25/09/2024 Latest

Latest

The version published at this time contains new features related to the INSPIRE Reference Validator and the Validator UI, please see them in detail:

🚀 New Features

#1116 Include data-service linking simplification for WFS/ATOM - #854

🚀 Validator UI

Validator UI upgrade from ECL v3 to ECL v4
Remove choice between MD TG 1.3 and TG 2.0

Deployment instructions

The section containing the deployment process using Docker image and troubleshooting section. You can also find these in the training material

docker login docker.pkg.github.com 
#Provide Github credentials
docker run --name inspire-validator -d -p 8090:8090 -v ~/etf:/etf docker.pkg.github.com/inspire-mif/helpdesk-validator/inspire-validator:2024.3
#Launches a container with the image, exposing the UI in port 8090 through the same port in the host machine, and uses a volume in the local file system, on the directory ~/etf,  this will create an ~/etf folder inside the user home folder.

Once the INSPIRE Reference Validator has fully loaded, we can access to it through the URL http://localhost:8090/validator/home/index.html

Please note that installation instructions for apt-get include --allow-unauthenticated parameter because the certificate of the Debian repository has expired, so this parameter is needed to download and install the tools properly.

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 (inside the ETF docker folder) the command

docker build . -t [IMAGE_NAME]:[VERSION]

You can run this again using the run command

docker run --name inspire-validator -d -p 8090:8090 -v ~/etf:/etf [IMAGE_NAME]:[VERSION]

Deployment on production host

The Docker image is set up to run at localhost to be deployed on any machine. However, users may need to access their validator on a dedicated host, usually with a domain name. For proper functioning of the validator, the UI and correct rendering of Test Reports, the 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.
It is also necessary to configure the Validator UI properties in order to properly point to the ETF. Thus, it is necessary to modify the configuration values in the /validator/js/config.js file inside the ui.zip (to point to the corresponding host domain).
Then you can proceed to the build process described in the previous point.

Since 22/12/2022 OGC moved to production version 5.5.2 (2022-08-26) of the TEAM Engine, which introduced credentials for the calls to the services.
Thus, any deployment which makes use of the OGC TEAM Engine needs to introduce credentials (to be requested here) in order to use them.
We have incorporated three parameters in the /WEB-INF/classes/etf-config.properties file of validator.war that need to be filled accordingly to authorize the use of the services:

#TEAM Engine credentials of your organization in order to properly use TEAM Engine remote calls
etf.testdrivers.teamengine.url = http://cite.opengeospatial.org/teamengine
etf.testdrivers.teamengine.username = 
etf.testdrivers.teamengine.password =

Exposing the validator through a proxy

Usually, host machines are connected to a private network that accesses 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-2024.3.zip and follow the instructions in the README.md file inside the .zip file.

Setting up a cache of INSPIRE Registry resources

In your own deployment you may want to increase the performance of fetching the different resources that the INSPIRE Reference Validator requires from the INSPIRE Registry for validations.

Attached is the file inspire-registry-resources.zip, which includes the resources that the INSPIRE Reference Validator requests to the INSPIRE Registry to execute the validations defined in the Executable Test Suites (ETSs).
Using this content, you may configure your own deployment to access these resources without the need to make a call to the INSPIRE Registry to obtain them, increasing the performance of your own instance while decreasing the dependency on external resources in your installation.

Example of setting up INSPIRE Registry resources as cache

In order to show how to use the Registry resources as cache, we have prepared a simple example.
The purpose of this example is to provide a foundation that can be adapted to an organization's proxy policies.

Download the Registry resources below.
Unzip the resources.
Open a terminal and access the resources folder
Publish the resources as an http server using, for example, Python:
python -m http.server 8000
Once the resources are published, we can use any proxy reverse (nginx, apache, ...). We show you an example using fiddle:
function OnBeforeRequest(oSession: Session) { if (oSession.host == "inspire.ec.europa.eu") { oSession.host = "0.0.0.0"; oSession.port = 8000; oSession.url = oSession.url.replace("https://inspire.ec.europa.eu", "http://0.0.0.0:8000"); } }

This will ensure that all the Validator's requests to the Registry are redirected to the server, using these local Registry resources instead.

Assets 5

08 Jul 07:19

jenriquesoriano

v2024.2

07e6494

v2024.2 - 11/07/2024

The version published at this time contains new features and non-breaking changes related to the INSPIRE Reference Validator.

🚀 New Features

#1067 Data set - TG Document links updated #846 #849
#1098 Support to data-service linking simplification for WMS included #845

🐛 Bugfixes

#1081 docker-entrypoint.sh
#1085 Predefined Atom - TG Requirement 42 condition fixed #847
#1099 Check on MetadataURL fixed #845

🚀 Validator UI

#47 Remove beta instance entry from the menu
#48 Update ATS links to point to their respective master branches
#94 Remove search file from the header #93

Deployment instructions

The section containing the deployment process using Docker image and troubleshooting section. You can also find these in the training material

docker login docker.pkg.github.com 
#Provide Github credentials
docker run --name inspire-validator -d -p 8090:8090 -v ~/etf:/etf docker.pkg.github.com/inspire-mif/helpdesk-validator/inspire-validator:2024.2
#Launches a container with the image, exposing the UI in port 8090 through the same port in the host machine, and uses a volume in the local file system, on the directory ~/etf,  this will create an ~/etf folder inside the user home folder.

Once the INSPIRE Reference Validator has fully loaded, we can access to it through the URL http://localhost:8090/validator/home/index.html

Modifying the Docker image

docker build . -t [IMAGE_NAME]:[VERSION]

You can run this again using the run command
`
docker run --name inspire-validator -d -p 8090:8090 -v ~/etf:/etf [IMAGE_NAME]:[VERSION]

##### Deployment on production host

The Docker image is set up to run at localhost to be deployed on any machine. However, users may need to access their validator on a dedicated host, usually with a domain name. For proper functioning of the validator, the UI and correct rendering of Test Reports, the 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. 
It is also necessary to configure the Validator UI properties in order to properly point to the ETF. Thus, it is necessary to modify the configuration values in the /validator/js/config.js file inside the ui.zip (to point to the corresponding host domain).
Then you can proceed to the build process described in the previous point.

Since 22/12/2022 OGC moved to production [version 5.5.2 (2022-08-26)](https://opengeospatial.github.io/teamengine/relnotes.html) of the [TEAM Engine](http://cite.opengeospatial.org/teamengine/), which introduced credentials for the calls to the services.
Thus, any deployment which makes use of the OGC TEAM Engine needs to introduce credentials (to be requested [here](https://cite.opengeospatial.org/teamengine/register.jsp)) in order to use them.
We have incorporated three parameters in the _/WEB-INF/classes/etf-config.properties_ file of _validator.war_ that need to be filled accordingly to authorize the use of the services:

#TEAM Engine credentials of your organization in order to properly use TEAM Engine remote calls
etf.testdrivers.teamengine.url = http://cite.opengeospatial.org/teamengine
etf.testdrivers.teamengine.username =
etf.testdrivers.teamengine.password =


##### Exposing the validator through a proxy

Usually, host machines are connected to a private network that accesses 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-2024.2.zip and follow the instructions in the README.md file inside the .zip file.

##### Setting up a cache of INSPIRE Registry resources

In your own deployment you may want to increase the performance of fetching the different resources that the INSPIRE Reference Validator requires from the INSPIRE Registry for validations.

Attached is the file inspire-registry-resources.zip, which includes the resources that the INSPIRE Reference Validator requests to the INSPIRE Registry to execute the validations defined in the Executable Test Suites (ETSs).
Using this content, you may configure your own deployment to access these resources without the need to make a call to the INSPIRE Registry to obtain them, increasing the performance of your own instance while decreasing the dependency on external resources in your installation.

Assets 5

09 May 15:33

jenriquesoriano

v2024.1

d2e9b7f

v2024.1 - 09/05/2024

The version published at this time contains new features and non-breaking changes related to the INSPIRE Reference Validator.

🚀 New Features

Architecture and technological components update. This version has undergone a technological update of its components, as well as a reengineering of the architecture to simplify its use and maintenance at the software product level. The main updated elements have been:
- Base Docker image jetty:10.0.18-jre11-alpine-eclipse-temurin (Alpine Linux v3.18)
- Apache 2.4.59
- Squid 5.9
- nginx server has been removed to simplify the architecture and facilitate its maintenance.
- Jetty 10.0.8
- Java version Temurin-11.0.21
- ETF libraries update

#1046 HH - Changes from 1089 amendment #833
#1048 SU Vector - Changes from 1089 amendment #826
#1049 SU Grid - Changes from 1089 amendment #835
#1050 LC - Changes from 1089 amendment #836
#1052 HY - Changes from 1089 amendment #837
#1066 Use of the CRS register - Changes from 1089 amendment #839

🐛 Bugfixes

#1028 SD - Attribute localSpeciesName not recognized as void #838
#1042 Blue header and footer too wide and fixed in results page, information window too narrow (2024.0.1) #68

🚀 Validator UI

49 Large names in the UI are not wrapped
75 Look & Feel
77 Label for CC8 not available on the re-run page
78 Error on re-run page for services
80 Test run page-header and footer too wide
83 Some ETS names not appearing on rerun
84 WFS advanced options not appearing
85 Remove double import of captcha javascript
86 Look and feel adaptations

Deployment instructions

The section containing the deployment process using Docker image and troubleshooting section. You can also find these in the training material

docker login docker.pkg.github.com 
#Provide Github credentials
docker run --name inspire-validator -d -p 8090:8090 -v ~/etf:/etf docker.pkg.github.com/inspire-mif/helpdesk-validator/inspire-validator:2024.1
#Launches a container with the image, exposing the UI in port 8090 through the same port in the host machine, and uses a volume in the local file system, on the directory ~/etf,  this will create an ~/etf folder inside the user home folder.

Once the INSPIRE Reference Validator has fully loaded, we can access to it through the URL http://localhost:8090/validator/home/index.html

Modifying the Docker image

docker build . -t [IMAGE_NAME]:[VERSION]

You can run this again using the run command

docker run --name inspire-validator -d -p 8090:8090 -v ~/etf:/etf [IMAGE_NAME]:[VERSION]

Deployment on production host

#TEAM Engine credentials of your organization in order to properly use TEAM Engine remote calls
etf.testdrivers.teamengine.url = http://cite.opengeospatial.org/teamengine
etf.testdrivers.teamengine.username = 
etf.testdrivers.teamengine.password =

Exposing the validator through a proxy

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-2024.1.zip and follow the instructions in the README.md file inside the .zip file.

Setting up a cache of INSPIRE Registry resources

In your own deployment you may want to increase the performance of fetching the different resources that the INSPIRE Reference Validator requires from the INSPIRE Registry for validations.

Assets 5

06 Mar 12:33

jenriquesoriano

v2024.0.1

3518f7b

v2024.0.1 - 06/03/2024

The version published at this time contains non-breaking changes related to the INSPIRE Reference Validator.

🚀 New Features

#1012 INSPIRE Validator does not recognize ATOM certificate - Slovakia
#1035 Information on version visible to user

🐛 Bugfixes

#1033 Validator v. 2024.0 fails when choosing "Conformance Class 2c: 'INSPIRE data sets and data set series metadata for IACS'"

🚀 Validator UI

#58 WCAG Accessibility adaptations
#60 Errors in CC2b and CC2c
#63 Information version visible to the user
#66 Frame of the test report very tight
#69 FOOTER-Update JRC unit
#70 FOOTER-Update accesibility link

Deployment instructions

The section containing the deployment process using Docker image and troubleshooting section. You can also find these in the training material

docker login docker.pkg.github.com 
#Provide Github credentials
docker run --name inspire-validator -d -p 8090:8090 -v ~/etf:/etf docker.pkg.github.com/inspire-mif/helpdesk-validator/inspire-validator:2024.0.1
#Launches a container with the image, exposing the UI in 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

docker build -t [IMAGE_NAME]:[VERSION]

You can run this again using the run command

docker run --name inspire-validator -d -p 8090:8090 -v ~/etf:/etf [IMAGE_NAME]:[VERSION]

Deployment on production host

#TEAM Engine credentials of your organization in order to properly use TEAM Engine remote calls
etf.testdrivers.teamengine.url = http://cite.opengeospatial.org/teamengine
etf.testdrivers.teamengine.username = 
etf.testdrivers.teamengine.password =

Exposing the validator through a proxy

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-2024.0.1.zip and follow the instructions in the README.md file inside the .zip file.

Setting up a cache of INSPIRE Registry resources

In your own deployment you may want to increase the performance of fetching the different resources that the INSPIRE Reference Validator requires from the INSPIRE Registry for validations.

Assets 5

22 Feb 16:05

jenriquesoriano

v2024.0

3518f7b

v2024.0 - 22/02/2024

The version published at this time contains non-breaking changes related to the INSPIRE Reference Validator.

🚀 New Features

#1009 INSPIRE data sets and data set series linked service metadata - #822
#1008 Added certificate for Spanish Agrarian Guarantee Fund
#1012 Added certificate for Úrad geodézie, kartografie a katastra SR
#1027 Data set XSD Schemas updated - #824

🚀 Validator UI

#53 Incorporate CC8 to the Validator UI
#58 WCAG Accessibility adaptations

Deployment instructions

The section containing the deployment process using Docker image and troubleshooting section. You can also find these in the training material

docker login docker.pkg.github.com 
#Provide Github credentials
docker run --name inspire-validator -d -p 8090:8090 -v ~/etf:/etf docker.pkg.github.com/inspire-mif/helpdesk-validator/inspire-validator:2024.0
#Launches a container with the image, exposing the UI in 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

docker build -t [IMAGE_NAME]:[VERSION]

You can run this again using the run command

docker run --name inspire-validator -d -p 8090:8090 -v ~/etf:/etf [IMAGE_NAME]:[VERSION]

Deployment on production host

#TEAM Engine credentials of your organization in order to properly use TEAM Engine remote calls
etf.testdrivers.teamengine.url = http://cite.opengeospatial.org/teamengine
etf.testdrivers.teamengine.username = 
etf.testdrivers.teamengine.password =

Exposing the validator through a proxy

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-2024.0.zip and follow the instructions in the README.md file inside the .zip file.

Setting up a cache of INSPIRE Registry resources

In your own deployment you may want to increase the performance of fetching the different resources that the INSPIRE Reference Validator requires from the INSPIRE Registry for validations.

Assets 5

19 Sep 11:00

jenriquesoriano

v2023.3

483728b

v2023.3 - 18/09/2023

The version published at this time contains non-breaking changes related to the INSPIRE Reference Validator.

🐛 Bugfixes

#823 SNI Error validating services
#642 Problem with the test case "OpenSearch Description Query examples for each dataset" of predefined-ATOM - #815

🚀 Validator UI

#47 Remove beta instance entry from the menu

Deployment instructions

The section containing the deployment process using Docker image and troubleshooting section. You can also find these in the training material

docker login docker.pkg.github.com 
#Provide Github credentials
docker run --name inspire-validator -d -p 8090:8090 -v ~/etf:/etf docker.pkg.github.com/inspire-mif/helpdesk-validator/inspire-validator:2023.3
#Launches a container with the image, exposing the UI in 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

docker build -t [IMAGE_NAME]:[VERSION]

You can run this again using the run command

docker run --name inspire-validator -d -p 8090:8090 -v ~/etf:/etf [IMAGE_NAME]:[VERSION]

Deployment on production host

#TEAM Engine credentials of your organization in order to properly use TEAM Engine remote calls
etf.testdrivers.teamengine.url = http://cite.opengeospatial.org/teamengine
etf.testdrivers.teamengine.username = 
etf.testdrivers.teamengine.password =

Exposing the validator through a proxy

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-2023.3.zip and follow the instructions in the README.md file inside the .zip file.

Setting up a cache of INSPIRE Registry resources

In your own deployment you may want to increase the performance of fetching the different resources that the INSPIRE Reference Validator requires from the INSPIRE Registry for validations.

Assets 5

21 Jun 10:29

jenriquesoriano

v2023.2

29ed25e

v2023.2 - 21/06/2023

The version published at this time contains breaking and non-breaking changes.

🚀 New Features

#965 Upgrade INSPIRE Reference Validator to Java 11

🐛 Bugfixes

#113 tn-as.c.1 significantPoint exception added for air TransportNode - #813
#382 HH.HealthDeterminantMeasure.Default option style added - #814
#722 #751 #758 #819 TG Req 43 and TG Req 44 updated - #815
#928 Keyword split into INSPIRE data theme and GEMET - #816
#943 am-as.b.2 competentAuthority xsi:nil condition added - #817
#950 Wrong polygon orientation reported for CRS EPSG:3045/EPSG:4258 - #4 #30
#961 CAPTCHA does not work
#963 API call added to IA and AS themes - #818

🚀 Validator UI

#45 Update captcha verification endpoint

Deployment instructions

The section containing the deployment process using Docker image and troubleshooting section. You can also find these in the training material

docker login docker.pkg.github.com 
#Provide Github credentials
docker run --name inspire-validator -d -p 8090:8090 -v ~/etf:/etf docker.pkg.github.com/inspire-mif/helpdesk-validator/inspire-validator:2023.2
#Launches a container with the image, exposing the UI in 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

docker build -t [IMAGE_NAME]:[VERSION]

You can run this again using the run command

docker run --name inspire-validator -d -p 8090:8090 -v ~/etf:/etf [IMAGE_NAME]:[VERSION]

Deployment on production host

#TEAM Engine credentials of your organization in order to properly use TEAM Engine remote calls
etf.testdrivers.teamengine.url = http://cite.opengeospatial.org/teamengine
etf.testdrivers.teamengine.username = 
etf.testdrivers.teamengine.password =

Exposing the validator through a proxy

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-2023.2.zip and follow the instructions in the README.md file inside the .zip file.

Setting up a cache of INSPIRE Registry resources

In your own deployment you may want to increase the performance of fetching the different resources that the INSPIRE Reference Validator requires from the INSPIRE Registry for validations.

Assets 5

16 Mar 15:51

jenriquesoriano

v2023.1

29ed25e

v2023.1 - 16/03/2023

The version published at this time contains breaking and non-breaking changes.

🐛 Bugfixes

#141 md sds 3.6 Coupled Resource manual check added - #806
#849 tn-as.c.1 geometry manual check added - #802
#898 bu-as.a.11 currentUse valid_href path fixed - #803
#927 Citation Date also allows gco:DateTime - #804
#930 new features paths added in inspire and inspire-noggeo - #805
#545 Permanent Test run failure of ETF-based Tests in the GDI-DE Testsuite due to „SSL read failed“ from inspire.ec.europa.eu - Included inspire-registry-resources.zip file in the release

Deployment instructions

The section containing the deployment process using Docker image and troubleshooting section. You can also find these in the training material

docker login docker.pkg.github.com 
#Provide Github credentials
docker run --name inspire-validator -d -p 8090:8090 -v ~/etf:/etf docker.pkg.github.com/inspire-mif/helpdesk-validator/inspire-validator:2023.1
#Launches a container with the image, exposing the UI in 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

docker build -t [IMAGE_NAME]:[VERSION]

You can run this again using the run command

docker run --name inspire-validator -d -p 8090:8090 -v ~/etf:/etf [IMAGE_NAME]:[VERSION]

Deployment on production host

#TEAM Engine credentials of your organization in order to properly use TEAM Engine remote calls
etf.testdrivers.teamengine.url = http://cite.opengeospatial.org/teamengine
etf.testdrivers.teamengine.username = 
etf.testdrivers.teamengine.password =

Exposing the validator through a proxy

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-2023.1.zip and follow the instructions in the README.md file inside the .zip file.

Setting up a cache of INSPIRE Registry resources

In your own deployment you may want to increase the performance of fetching the different resources that the INSPIRE Reference Validator requires from the INSPIRE Registry for validations.

Assets 5

25 Jan 14:07

jenriquesoriano

v2023.0

fa09a8e

v2023.0 - 25/01/2023

The version published at this time contains breaking and non-breaking changes.

🐛 Bugfixes

#559 #912 ad, au, cp, hy and tn http redirections fixed - #787
#661 #637 application/atom+xml and text/xml added as valid types - #788
#852 hy-n-as.b.1 geometry manual check - #789
#854 noAccessText error message updated - #790
#873 Topic category validation fixed - #791
#883 nz-ia.a.2 SpecificExposedElementTypeValue path fix - #792
#900 WFS Direct dependency updated - #793
#881 Docker deployment issue - Docker deployment instructions updated

🚀 Validator UI

#35 Modify default parameters in metadata urls to ensure ISO compliance - #41
#31 Wrong dependency between WFS Conformance Classes - #43
#30 Indications on the time that tests reports are kept - #40
#29 Wrong title in the single test report page - #39
#26 "Resource type" filter does not work in production - #38

Deployment instructions

The section containing the deployment process using Docker image and troubleshooting section. You can also find these in the training material

docker login docker.pkg.github.com 
#Provide Github credentials
docker run --name inspire-validator -d -p 8090:8090 -v ~/etf:/etf docker.pkg.github.com/inspire-mif/helpdesk-validator/inspire-validator:2023.0
#Launches a container with the image, exposing the UI in 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

docker build -t [IMAGE_NAME]:[VERSION]

You can run this again using the run command

docker run --name inspire-validator -d -p 8090:8090 -v ~/etf:/etf [IMAGE_NAME]:[VERSION]

Deployment on production host

#TEAM Engine credentials of your organization in order to properly use TEAM Engine remote calls
etf.testdrivers.teamengine.url = http://cite.opengeospatial.org/teamengine
etf.testdrivers.teamengine.username = 
etf.testdrivers.teamengine.password =

Exposing the validator through a proxy

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-2023.0.zip and follow the instructions in the README.md file inside the .zip file.

Assets 4

21 Sep 13:43

jenriquesoriano

v2022.3

c10e687

v2022.3 - 21/09/2022

The version published at this time contains non-breaking changes.

🐛 Bugfixes

#39 #613 #822 at39bis layer title manual check added - #777
#683 at03 check changed to manual and message updated - #769
#788 wfs:member additionalObjects path added - #770
#798 sd:SpeciesDistributionUnit added in sd-gml.a.1 - #771
#809 af:Site added in af-gml.a.1 - #772
#816 BuildingPart added in bu-gml-a.1 - #773
#824 C15 codeListValue and error message updated - #774
#830 sr-as.b.3 Polygon, PolyhedralSurface and TriangulatedSurface added - #775
#844 wms and wmts description links updated - #776

Deployment instructions

The section containing the deployment process using Docker image and troubleshooting section. You can also find these in the training material

docker login docker.pkg.github.com 
#Provide Github credentials
docker run --name inspire-validator -d -p 8090:8090 -v ~/etf:/etf docker.pkg.github.com/inspire-mif/helpdesk-validator/inspire-validator:2022.3
#Launches a container with the image, exposing the UI in 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

docker build -t [IMAGE_NAME]:[VERSION]

You can run this again using the run command

docker run --name inspire-validator -d -p 8090:8090 -v ~/etf:/etf [IMAGE_NAME]:[VERSION]

Deployment on production host

Exposing the validator through a proxy

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-2022.3.zip and follow the instructions in the README.md file inside the .zip file.

Assets 4

Releases: INSPIRE-MIF/helpdesk-validator

v2024.3 - 25/09/2024

🚀 New Features

🚀 Validator UI

Deployment instructions

Modifying the Docker image

Deployment on production host

Exposing the validator through a proxy

Setting up a cache of INSPIRE Registry resources

Example of setting up INSPIRE Registry resources as cache

v2024.2 - 11/07/2024

🚀 New Features

🐛 Bugfixes

🚀 Validator UI

Deployment instructions

Modifying the Docker image

v2024.1 - 09/05/2024

🚀 New Features

🐛 Bugfixes

🚀 Validator UI

Deployment instructions

Modifying the Docker image

Deployment on production host

Exposing the validator through a proxy

Setting up a cache of INSPIRE Registry resources

v2024.0.1 - 06/03/2024

🚀 New Features

🐛 Bugfixes

🚀 Validator UI

Deployment instructions

Modifying the Docker image

Deployment on production host

Exposing the validator through a proxy

Setting up a cache of INSPIRE Registry resources

v2024.0 - 22/02/2024

🚀 New Features

🚀 Validator UI

Deployment instructions

Modifying the Docker image

Deployment on production host

Exposing the validator through a proxy

Setting up a cache of INSPIRE Registry resources

v2023.3 - 18/09/2023

🐛 Bugfixes

🚀 Validator UI

Deployment instructions

Modifying the Docker image

Deployment on production host

Exposing the validator through a proxy

Setting up a cache of INSPIRE Registry resources

v2023.2 - 21/06/2023

🚀 New Features

🐛 Bugfixes

🚀 Validator UI

Deployment instructions

Modifying the Docker image

Deployment on production host

Exposing the validator through a proxy

Setting up a cache of INSPIRE Registry resources

v2023.1 - 16/03/2023

🐛 Bugfixes

Deployment instructions

Modifying the Docker image

Deployment on production host

Exposing the validator through a proxy

Setting up a cache of INSPIRE Registry resources

v2023.0 - 25/01/2023

🐛 Bugfixes

🚀 Validator UI

Deployment instructions

Modifying the Docker image

Deployment on production host

Exposing the validator through a proxy

v2022.3 - 21/09/2022

🐛 Bugfixes

Deployment instructions

Modifying the Docker image

Deployment on production host

Exposing the validator through a proxy