Please refer to the following instructions and tips to run the puris application. Per TRG we recommend the installation via helm.
First configure the application to your needs. you can use the default values.yaml as a basis. Please find below the most relevant configurations:
- Ingress (if you want to enable ingress) for frontend/backend, under
frontend.ingress.
andbackend.ingress.
- EDC, under
backend.puris.edc
- DTR incl. keycloak under
backend.puris.dtr
- Own master data, under
backend.puris.own
- Role demonstration setup, under
backend.puris.demonstrator.role
- Postgresql settings, under
backend.puris.datasource
(only necessary, ifpostgres.enabled
is false - else autoconfigured). - Frontend Keycloak is disabled by default but can be configured under
frontend.puris.keycloak
.
NOTE
Further information on the individual properties and the installation commands can be found in the following README.md.
Attention: When using postgres.enabled
= false and bringing your own database, ensure to set
backend.puris.jpa.hibernate.ddl-auto
= validate
to prevent DATA LOSS.
See the INSTALL.md
files in the backend and frontend folder.
See Install.md
file in folder local for integration testing environment with two
deployed applications and EDCs.
This work is licensed under the Apache-2.0.
- SPDX-License-Identifier: Apache-2.0
- SPDX-FileCopyrightText: 2024 Contributors to the Eclipse Foundation
- Source URL: https://github.com/eclipse-tractusx/puris