From 054acf4a2968dbeb03247a31aeedd647a5a24ded Mon Sep 17 00:00:00 2001
From: Martin Weise <martin.weise@tuwien.ac.at>
Date: Mon, 6 Nov 2023 21:09:06 +0100
Subject: [PATCH] Added more documentation

---
 .docs/deployment-helm.md | 6 +++++-
 1 file changed, 5 insertions(+), 1 deletion(-)

diff --git a/.docs/deployment-helm.md b/.docs/deployment-helm.md
index f31fef5a85..c7164af43a 100644
--- a/.docs/deployment-helm.md
+++ b/.docs/deployment-helm.md
@@ -31,7 +31,7 @@ The helm chart depends on four components:
 ## Configuration before the installation
 
 Define an admin user that the services can use to communicate with 
-the [authentication service](../system-services-authentication). You will need to manually create this user later after
+the [Authentication Service](../system-services-authentication). You will need to manually create this user later after
 the installation.
 
 ## Configuration after the installation
@@ -55,6 +55,10 @@ the [authentication service](../system-services-authentication) as `admin` and:
 3. Assign this user the role `admin`.
 4. Delete the user `admin`.
 
+Then import the DBRepo realm by clicking the dropdown "master" > Create Realm and import 
+the [`dbrepo-realm.json`](https://gitlab.phaidra.org/fair-data-austria-db-repository/fda-services/-/raw/dev/dbrepo-authentication-service/dbrepo-realm.json)
+by uploading the file *or* copying the contents and click "Create".
+
 ### Backup
 
 tbd
-- 
GitLab