Nested configuration doesn't work

[markwilkinson]

Following the documentation here: https://fairdatapoint.readthedocs.io/en/latest/deployment/advanced-configuration.html#running-fdp-on-a-nested-route

hypothetical path: /example

the FDP Client reports (in the docker-compose logs) attempting to reach /usr/share/nginx/html/example This doesn't exist, which I confirmed by shelling-in to the container. If I take the content of /html/ and copy it all into /html/example in the container, then the error goes away. There is still a 301 reported by the FDP client, but that never reaches me (I am investigating why that happens, but it may be a network config problem on my end...)

[markwilkinson]

Naaaa... it doesn't work, even with the copying into the /html/example folder. The actuator can't be found, so the lookup in GraphDB always fails.

Note also that the logo is not linked to the correct location (should be in /example/assets, but links directly to /assets/ in the HTML page from FDP)