Updated README.md

Signed-off-by: Dennis Labordus <[email protected]>

Author: Dennis Labordus

README.md

@@ -16,7 +16,7 @@ To start all configured services using BaseX, run the following two commands:
 
 ```
 # Build (if needed) and start all the containers in the background.
-docker-compose -f compas/docker-compose-basex.yml up -d --build
+docker-compose --env-file compas/.env -f compas/docker-compose-basex.yml up -d --build
 ```
 
 This command will first build the custom images for Keycloak and the Reverse Proxy and then start all containers.
@@ -50,7 +50,7 @@ To start all configured services using PostgreSQL, run the following two command
 
 ```
 # Build (if needed) and start all the containers in the background.
-docker-compose -f compas/docker-compose-postgresql.yml up -d --build
+docker-compose --env-file compas/.env -f compas/docker-compose-postgresql.yml up -d --build
 ```
 
 This command will first build the custom images for Keycloak and the Reverse Proxy and then start all containers.
@@ -87,10 +87,6 @@ The following Keycloak attributes have been added:
 - **CRUD roles for the SCL Data Service**: Create, Read, Update and Delete roles have been added to the SCL Data Service client.
 When interacting with the SCL Data Service, a JWT token needs to have certain roles before interaction is possible. 
 These roles are assigned to certain users (see below).
-- **CoMPAS Group**: A CoMPAS demo group has been added.
-- **A Demo User**: A Demo user without specific roles.
-  - Username: 'user'
-  - Password: 'user'.
 - **A SCL Data Editor**: A user with the roles 'Create', 'Read', 'Update' and 'Delete'. This way, it has read and write access to the SCL Data Service.
   - Username: scl-data-editor
   - Password: editor