- Any new added administrator should belong to the groups
lds, and have its SSH key set up.
- The files of the deployment (
/opt/medco) have the group
- Updates of the system should be regularly done.
- After a reboot, the MedCo deployment will not persist and must be started manually.
- While the renewal of the certificate may be done automatically with Let's Encrypt, it is not automatically set up in the MedCo deployment, thus every 2-3 months this should be updated.
- The Keycloak of the deployment is set up to demonstrate the connection with SwitchAAI. This includes having some keys configured in Keycloak, so be careful to not wipe the database in order to not loose those keys, otherwise the configuration will have to be redone.
Connect with SSH to the machine (you should have your SSH key set up there).
Ensure the configuration specific to the MedCo stays (see next section).
Update the configuration according to the following examples. For the passwords, use the same as defined in the previous deployments.
- "GB_FOOTER_TEXT=Disclaimer: This demo complies with the EPFL regulations and guidelines regarding the storage and use of personal data: https://www.epfl.ch/about/overview/overview/regulations-and-guidelines/"
Get them from the Google Drive folder and execute the script.
./scripts/load-i2b2csv-data.sh test/data/spo-synthetic/node_0 localhost i2b2medcosrv0 medcoconnectorsrv0
./scripts/load-i2b2csv-data.sh test/data/spo-synthetic/node_1 localhost i2b2medcosrv1 medcoconnectorsrv1
./scripts/load-i2b2csv-data.sh test/data/spo-synthetic/node_2 localhost i2b2medcosrv2 medcoconnectorsrv2
The certificate is provided by Let's Encrypt and valid for a period of 3 months, it thus needs regular renewing. First ensure that the configuration located in
Then with sudo rights renew the certificate:
cp /etc/letsencrypt/live/medco-demo.epfl.ch/fullchain.pem \
cp /etc/letsencrypt/live/medco-demo.epfl.ch/privkey.pem \
And finally restart the stack: