Skip to content

Latest commit

 

History

History
71 lines (51 loc) · 2.86 KB

maintenance.md

File metadata and controls

71 lines (51 loc) · 2.86 KB

Maintenance

Syncing Elexis Users

To sync users of an existing Elexis database with keycloak, execute ./ee setup sync_users_es_keycloak. In EE every user must have a unique e-mail address. If a user does not have an associated e-mail address, syncing will generate one in the format userid@ORGANSATION_DOMAIN.

Backup

The following service data is stored (as docker volumes) within the elexis-environment:

  • LDAP
    • Storage
    • Configuration
  • Rocketchat
    • Database
    • File-Uploads
  • Bookstack
    • File-Uploads
  • Elexis-Server
    • Home

Execute ee system backup to back-up data into site/backup. The SQL databases are not part of the backup, you have to take care of them by yourself.

Restore

Execute ee system restore on the tarfile generated during the previous process.

Updating an existing EE installation

In order to update an existing installation, perform the following steps:

  1. Shut down the elexis-environment: ./ee system cmd stop
  2. Delete all existing containers: ./ee system cmd rm -f
  3. (Optional) remove unused images (to free space): docker image prune
  4. Fetch the current version from the respository :git pull
  5. Update the configuration image: docker pull medevit/eenv-config
  6. Bring .env up-to-date: ./ee setup configure
  7. Pull current version images: ./ee system cmd pull --include-deps
  8. Start EE with new containers being built: ./ee system cmd up -d --build

Upgrading an existing EE installation

In order to upgrade an existing installation, stop EE and execute clean ./ee system clean. Then call ./ee setup ee_upgrade_site to switch to the next higher branch.

Specific upgrade remarks

Upgrade from R2 to R3

Moving docker data to another filesystem

We will move the docker default volumes directory to a new directory.

  1. Shut down EE
  2. Edit /lib/systemd/system/docker.service and modify ExecStart to add --data-root /docker/volumes
  3. Stop docker systemctl stop docker
  4. Ensure docker is stopped: Check via ps aux | grep -i docker | grep -v grep no output should follow
  5. Reload docker configuration systemctl daemon-reload
  6. mv -v /var/lib/docker/* /docker/data/
  7. Start docker systemctl start docker
  8. Check volumes are still there docker volume ls

Initialize an empty harddisk

Steps to initialize a fresh harddisk with LVM and ext4