From 04088c6186b7b986e08dc170b6139516e4a0f5b5 Mon Sep 17 00:00:00 2001 From: Omkar Zade <103944670+omkar-ethz@users.noreply.github.com> Date: Mon, 4 Aug 2025 13:33:52 +0000 Subject: [PATCH 1/2] (landingpage) add config keys for status-banner and support-email and an explanation --- services/landingpage/README.md | 2 ++ services/landingpage/config/config.json | 5 ++++- 2 files changed, 6 insertions(+), 1 deletion(-) diff --git a/services/landingpage/README.md b/services/landingpage/README.md index 81b2b822..a4bae1a8 100644 --- a/services/landingpage/README.md +++ b/services/landingpage/README.md @@ -14,6 +14,8 @@ In the default configuration [config.json file](./config/config.json), the landi For an explanation of how setting `BE_VERSION` changes the environment creation see [here](../../README.md#docker-compose-profiles-and-env-variables-configuration-options). +You can also add a footer with customizable `contactEmail` and a status banner with `statusCode = INFO | WARN | NONE` and a corresponding `statusMessage` as shown in [config.json](./config/config.json). All of these three settings are optional. + ## Enable additional features Setting the [BACKEND_HTTPS_URL and FRONTEND_HTTPS_URL env variables](../../.env) requires changing the `backend` and the `frontend` URL used by the `landingpage`. This is managed [here](../../entrypoints/merge_json.sh). diff --git a/services/landingpage/config/config.json b/services/landingpage/config/config.json index 1ed6b2ef..82e5a807 100644 --- a/services/landingpage/config/config.json +++ b/services/landingpage/config/config.json @@ -3,5 +3,8 @@ "doiBaseUrl": "http://landingpage.localhost/detail/", "facility": "facility", "scicatBaseUrl": "${FRONTEND_URL}", - "lbBaseUrl": "${BACKEND_URL}" + "lbBaseUrl": "${BACKEND_URL}", + "statusCode": "INFO", + "statusMessage": "This is a customizable status message", + "contactEmail": "support@scicat.eu" } From 73fde6e7e156eee0b847dee1538ecccaee03a9d0 Mon Sep 17 00:00:00 2001 From: Omkar Zade Date: Tue, 5 Aug 2025 13:52:17 +0200 Subject: [PATCH 2/2] Remove service specific config from landingpage README --- services/landingpage/README.md | 2 -- 1 file changed, 2 deletions(-) diff --git a/services/landingpage/README.md b/services/landingpage/README.md index a4bae1a8..81b2b822 100644 --- a/services/landingpage/README.md +++ b/services/landingpage/README.md @@ -14,8 +14,6 @@ In the default configuration [config.json file](./config/config.json), the landi For an explanation of how setting `BE_VERSION` changes the environment creation see [here](../../README.md#docker-compose-profiles-and-env-variables-configuration-options). -You can also add a footer with customizable `contactEmail` and a status banner with `statusCode = INFO | WARN | NONE` and a corresponding `statusMessage` as shown in [config.json](./config/config.json). All of these three settings are optional. - ## Enable additional features Setting the [BACKEND_HTTPS_URL and FRONTEND_HTTPS_URL env variables](../../.env) requires changing the `backend` and the `frontend` URL used by the `landingpage`. This is managed [here](../../entrypoints/merge_json.sh).