Issue deploying the validator in a production environment using a proxy

[geoportallux]

We have not managed to start the validator in our internal environment.

We are using Docker and Kubernetes to run the validator.

There are several issues:

Configuration

To configure the internal URL to be used, we have to make a custom dockerfile where we unpack the .war, replace the values in the config, repack a .war file and build a new image. That's not very dockeresque.

It would be easier to allow the use of environment variables or the possibility to mount a config file in a volume.

3 Things in one container => 3 Microservices.

The image you are building contains the validator, squid and apache, all in one container. That's not very dockeresque either. We need to configure http_proxy and https_proxy in our environment for the container to be able to connect to the internet. With the mix of the 3 services, this is hell, as you use it in your own context for another reason than the one we need it for.

Please split the 3 microservices into 3 images with a docker-compose file as an example.

Proxy

Please allow the use of the environment variables http_proxy and https_proxy (and maybe no_proxy) in your images.

In this way, everyone can deploy the validator in its own environment.