Table of Contents
Public configuration and definition of services to use DEMIS in a self-managed Kubernetes Cluster.
See ReleaseNotes for all information regarding the (newest) releases.
To use this stage-project in your Kubernetes cluster, you can use the project DEMIS-Development-Cluster. This project provides a complete setup of the DEMIS environment. To deploy the DEMIS cluster locally, you can follow the description in the README of the project.
By following the instructions from project DEMIS-Development-Cluster, you will be able to set up a local Kubernetes cluster with all the necessary components and configurations to run DEMIS. Additionally the stage-public repository will be checked out automatically by the command
make local init-stage
The Helm-Charts from the GitHub-Repository DEMIS-Helm-Charts are public. Therefore, you do not need any GitHub-Credentials to check out the repository. But to avoid to ran into rate-limits of GitHub, you can set your GitHub-Credentials in the files
- demis/credentials.tfvars
- idm/credentials.tfvars
- mesh/credentials.tfvars
You can set your GitHub-Credentials in this section:
#helm_repository_username = "USERNAME_HERE"
#helm_repository_password = "PASSWORD_HERE"
The DEMIS-Images from "docker.io/gematik1" are public and can be used without any credentials. But to avoid to ran into rate limits of DockerHub, you can set your Credentials in the files:
- demis/credentials.tfvars
- idm/credentials.tfvars
You can set your user_name, user_email and user_password in this section:
# docker_pull_secrets = [
# {
# name = "dockerhub-pull-secret"
# registry = "docker.io/gematik1"
# user_name = ""
# user_email = "[email protected]"
# user_password = "" # DockerHub-Access Token
# password_type = "plain"
# }
# ]
If you want to see the security policy, please check our SECURITY.md.
If you want to contribute, please check our CONTRIBUTING.md.
Copyright 2025 gematik GmbH
EUROPEAN UNION PUBLIC LICENCE v. 1.2
EUPL © the European Union 2007, 2016
See the LICENSE for the specific language governing permissions and limitations under the License
- Copyright notice: Each published work result is accompanied by an explicit statement of the license conditions for use. These are regularly typical conditions in connection with open source or free software. Programs described/provided/linked here are free software, unless otherwise stated.
- Permission notice: Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
- The copyright notice (Item 1) and the permission notice (Item 2) shall be included in all copies or substantial portions of the Software.
- The software is provided "as is" without warranty of any kind, either express or implied, including, but not limited to, the warranties of fitness for a particular purpose, merchantability, and/or non-infringement. The authors or copyright holders shall not be liable in any manner whatsoever for any damages or other claims arising from, out of or in connection with the software or the use or other dealings with the software, whether in an action of contract, tort, or otherwise.
- We take open source license compliance very seriously. We are always striving to achieve compliance at all times and to improve our processes. If you find any issues or have any suggestions or comments, or if you see any other ways in which we can improve, please reach out to: [email protected]
- Please note: Parts of this code may have been generated using AI-supported technology. Please take this into account, especially when troubleshooting, for security analyses and possible adjustments.
E-Mail to DEMIS Entwicklung