Integrate frontend

[MichaelLangbein]

• [x] clone code
• [x] create global .env with lots of annotations
• [x] build images
• [x] can frontend (which runs in a docker-compose) reach gfz-wps (which runs as a standalone-container)?
• [x] backend needs configuration: at wich urls are services to be reached?
• [x] integrate with rest of app

[MichaelLangbein]

@nbrinckm : i'll request a review once https://github.com/riesgos/buildall/pull/7 is merged.

[MichaelLangbein]

Aaaaall-right; Got the compose files working together. Reason it didn't work at first was that one file was on another path than the first. Docker compose tries to resolve relative paths in compose-files relative to the dir in wich the compose command is called ... which was off for dlr's compose-file, since that was in a sub-dir.

I'm currently getting an error from the backend-container, but that's a separate issue. Will fix that and then hopefully move on to another review.

[MichaelLangbein]

Docker compose tries to resolve relative paths in compose-files relative to the dir in wich the compose command is called ... which was off for dlr's compose-file, since that was in a sub-dir.

Seems that's not correct: relative paths are resolved relative to the first compose file used in the compose-command. See here: https://github.com/docker/compose/issues/4851

[MichaelLangbein]

Found an interesting problem.

• My backend-container is sending an execute-request to http://riesgos-wps:8080/wps/ProcessesingService (the WPS'es internal address)
• The wps responds with an ExecuteResponse with statusLocation=http://localhost:8082/wps/RetrieveResultServlet?id=... (the WPS'es external address)
• The backend-container attempts to fetch the result from http://localhost:8082/wps/RetrieveResultServlet?id=... but fails, since localhost is being looked for inside the backend-container.

For the backend to be able to talk to the WPSes, we'd need them to send back an ExecuteResponse with its docker-internal address.

On the other hand, if we want a WPS to be available to the outside world, we'd need it to respond with its external address. I think this latter problem can be solved with the upcoming proxy, though... ... I think that proxy might already be merged in main (btw thanks @nbrinckm ), so I'll try out that.