-
Notifications
You must be signed in to change notification settings - Fork 52
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
installation: document post-installation steps
- Loading branch information
Diego Rodriguez
committed
May 20, 2020
1 parent
9b99b25
commit f340b18
Showing
2 changed files
with
24 additions
and
3 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1 +1,22 @@ | ||
Thanks for flying REANA 🚀 | ||
|
||
The REANA system has been installed: | ||
|
||
There are a few steps left to finalise it's configuration | ||
|
||
1. Get the REANA-Server pod name: | ||
|
||
$ REANA_SERVER=$(kubectl get pod -l "app={{ .Release.Name }}-server" -o name -o jsonpath='{.items[0].metadata.name}') | ||
|
||
2. Initialise the database: | ||
|
||
$ kubectl exec $REANA_SERVER -- ./scripts/setup | ||
|
||
2. Create your administrator user and store the token: | ||
|
||
$ kubectl exec $REANA_SERVER -- flask reana-admin create-admin-user user@my.org | ||
<reana-admin-access-token-value> | ||
$ read -s REANA_ADMIN_ACCESS_TOKEN # paste the secret here | ||
$ kubectl create secret generic {{ .Release.Name }}-admin-access-token \ | ||
--from-literal=ADMIN_ACCESS_TOKEN='$REANA_ADMIN_ACCESS_TOKEN' | ||
|
||
Thanks for flying REANA 🚀 |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters