Landingpage

The SciCat provides standardised search on published datasets via this LandingPageServer

Configuration options

The landingpage configuration is set by the config files . Files inside the config folder, with a .json extension are merged respecting the alphabetical order of the files in the container .

Please note that merging the config files is a functionality provided by SciCat Live and is not supported natively by the landingpage .

Default configuration

In the default configuration config.json file , the landingpage is set to call the backend service available at backend.localhost (either v4 , by default, or v3 if specified otherwise by setting BE_VERSION ) and use the localhost frontend to redirect to the datasets details from the published data detail page.

For an explanation of how setting BE_VERSION changes the environment creation see the configuration options in the root docs .

Enable additional features

Setting the BACKEND_HTTPS_URL and FRONTEND_HTTPS_URL env variables requires changing the backend and the frontend URL used by the landingpage . This is managed in the entrypoint ../../entrypoints/merge_json.sh .

When setting LANDINGPAGE_HTTPS_URL it is likely you also want to set the BACKEND_HTTPS_URL and FRONTEND_HTTPS_URL , to allow the communication between the two wherever the browser is accessed.

With LANDINGPAGE_DEV=true (or DEV=true ), please use npm start -- --host 0.0.0.0 . This is to allow traffic from any IP to the landingpage component and it is necessary since the component runs in the docker network.

--profile 'search' instructs docker compose to create this additional service.