D4Science Infrastructure

mapproxy has a questionable documentation. There's a tool to autoconfigure services and layers, but when run against the paim geoserver it creates a configuration that does not validate:

KeyError: 'W_mpa'

I removed all the W_mpa: prefixes the it didn't like and I was then able to start the service. But it's not transparent.
It seems very powerful but it also needs a very carefully planned configuration. It could be very useful in the long term, but not something to set up hastly. I'll go back to varnish to see if it can help somewhat (the mapproxy documentation lists varnish as one of the recommended frontends, btw).

Both geoserver1-protectedareaimpactmaps.d4science.org and geoserver2-protectedareaimpactmaps.d4science.org are under a varnish instance right now.
One varnish instance for each geoserver, running locally. The flow is now:

haproxy -> nginx -> varnish -> geoserver

nginx was manually reconfigured, some work will be needed to integrate varnish completely.