Closed minottic closed 1 month ago
this is building from a local Dockerfile (the one you have in /Users/regina/Documents/work/scicatlive/LandingPageServer/Dockerfile
. What if you try to use this image? Does it work or gives any error?
will try it! no errors sofar. But what do I have up to now? I have not entered the DataCite credentials anywhere which should go to some .env of a SciCat BE I think.
there is a problem with this image, it contains configuration code, e.g. see https://github.com/SciCatProject/LandingPageServer/blob/develop/src/environments/environment.ts#L12 which fixes the backend connection. There are two options:
We go for the cleaner and more efficient option B.
I think the upstream already implements the option to pass config at run time. To double check, but if so, this is not blocked anymore by upstream
The idea was to adopt the working example of PSI for a setup of a LandingPage Server to DESY's specifics. Using scicatlive we aimed at including the setup of the new server as a another service in scicatlive. As very first step we exercised the setup locally (on a Mac). Following https://github.com/SciCatProject/scicatlive?tab=readme-ov-file#add-a-new-service we adopted for step 3 this compose.yaml
However before running it we made sure that
LandingPageServer
image builds.The build is successful using:
where it's clear that some adoptions still need to be made. My guess would be now to run the
compose.yaml
as mentioned above.