From 7c5b5530e995596ecc66581d3a1937754820f97e Mon Sep 17 00:00:00 2001 From: Alex Aperis Date: Mon, 4 Nov 2024 13:34:51 +0100 Subject: [PATCH] update readme --- README.md | 10 ++++------ 1 file changed, 4 insertions(+), 6 deletions(-) diff --git a/README.md b/README.md index 48a0cdd..da06e0c 100644 --- a/README.md +++ b/README.md @@ -31,22 +31,20 @@ grant-types: ["authorization_code"] post-logout-redirect-uris: ["http://localhost:8085/oidc/login"] ``` -Now that everything should be configured properly, from the root folder of the `starter-kit-lsaai-mock` run: +## Starting storage-and-interfaces with LS-AAI-mock + +From the root of the `starter-kit-storage-and-interfaces` folder and run: ```shell docker compose up -d ``` -## Starting storage-and-interfaces with LS-AAI-mock - -From the root of the `starter-kit-storage-and-interfaces` folder and run: +and then from the root folder of the `starter-kit-lsaai-mock` run: ```shell docker compose up -d ``` -Note that the above two commands need to be run in that specific order because the `LS-AAI-mock` compose creates the external network `my-app-network` which is used to communicate with the `aai-mock` service. - ## Starting the stack in standalone demo mode The file `docker-compose-demo.yml` is used to start the `storage-and-interfaces` services in *demo* mode with an example dataset preloaded and ingested to the sensitive data archive when the deployment is done. This comes with its own python implementation of a mock-oidc in place of LS-AAI and can be run as standalone for demonstration purposes.