You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Now that everything should be configured properly, from the root folder of the `starter-kit-lsaai-mock` run:
34
+
## Starting storage-and-interfaces with LS-AAI-mock
35
+
36
+
From the root of the `starter-kit-storage-and-interfaces` folder and run:
35
37
36
38
```shell
37
39
docker compose up -d
38
40
```
39
41
40
-
## Starting storage-and-interfaces with LS-AAI-mock
41
-
42
-
From the root of the `starter-kit-storage-and-interfaces` folder and run:
42
+
and then from the root folder of the `starter-kit-lsaai-mock` run:
43
43
44
44
```shell
45
45
docker compose up -d
46
46
```
47
47
48
-
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.
49
-
50
48
## Starting the stack in standalone demo mode
51
49
52
50
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.
0 commit comments