Elexis for server operation
- Removal of Shiro
- Security layer is now realized via Keycloak Filter
- Change of version handling. It is now merged with elexis-3-core
- DB Connection configuration via Environment Variables
- ES will not provide HTTPS services
- OpenID is not integrated in ES anymore
- Only product builds for linux x86_64 are made
If you want to operate ES standalone with authentication/authorization support, Elexis-Environment is your solution.
Requires maven 3.8 and java 17. Build can be started by executing mvn -f releng/es.parent/pom.xml clean verify -DskipTests -Delexis.branch=master
Documented in es.core.product.runtime.
You may either run this image using the enclosed docker-compose.yml file, or via a direct docker call.
For an overview of the available versions (tags), see https://hub.docker.com/r/medevit/elexis-server/tags/
Replace master with the resp. tag if another version is required.
To get a fresh and clean run of ES perform the following commands in the given order:
docker-compose rm -fRemove an already existing containerdocker volume rm elexis-server_elexis_homeRemove the volume holding the ES home-directorydocker-compose pullFetch the newest image of the serverdocker-compose upRun the server in foreground mode. Append-dto run in background.
docker run -e DEMO_MODE='true' -e TZ=Europe/Zurich -p 8380:8380 -p 7234:7234 medevit/elexis-server:masterAfter initially creating a container out of this image (which is what the run command does), note
the ID of the created instance, in order to restart it again afterwards. Repeatedly executing this command, always leaves
you with a newly generated container.
DISABLE_WEB_SECURITY=true(DC) or-e DISABLE_WEB_SECURITY='true'- disable the web security layerDEMO_MODE=true(DC) or-e DEMO_MODE='true'- download the demo database (only if not already downloaded)