verbis-admin
/
bridgehead
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Addressed Torben's comments to PR 52 

- Included email for CCP repositories.
- Used journalctl instead of docker ps for Bridgehead status.
This commit is contained in:
Croft 2023-01-27 11:08:00 +01:00
parent 7d9cec562e
commit 6123a9aeba
1 changed files with 8 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

11
README.md
View File

@ -85,7 +85,12 @@ Use "ccp" if you are in the DKTK network, the C4 network or the nNGM network.
In order to be able to install, you will need to have your own repository in GitLab for your site's configuration settings. This allows automated updates of the Bridgehead software.
To request a new repository, please send an email to bridgehead@helpdesk.bbmri-eric.eu. Mention which project you belong to, i.e. "bbmri" or "ccp", plus your chosen site name.
To request a new repository, please send an email to one of the following:
- For the bbmri project: bridgehead@helpdesk.bbmri-eric.eu.
- For the ccp project: support-ccp@dkfz-heidelberg.de
Mention which project you belong to, i.e. "bbmri" or "ccp", plus your chosen site name.
We will set the repository up for you. We will then send you:
@ -168,7 +173,7 @@ sudo systemctl [enable|disable] bridgehead@<PROJECT>.service
After starting the Bridgehead, you can watch the initialization process with the following command:
```shell
sudo journalctl -xefu bridgehead@bbmri.service
journalctl -u bridgehead@bbmri -f
```
if this exits with the following:
@ -188,7 +193,7 @@ docker ps
There should be 6 Docker proceses. If there are fewer, then you know that something has gone wrong. To see what is going on, run:
```shell
docker-compose -f bbmri/docker-compose.yml logs --follow
journalctl -u bridgehead@bbmri -f
```
Once the Bridgehead has passed these checks, take a look at the landing page: