Database settings & Quarkus DevServices

joahuber · August 17, 2022, 4:10pm

Hi
I have an issue using the Quarkus Integration. When starting Quarkus in Dev-Profile we do not specify the database URL and let Quarkus do the magic to spin up out database in a container. Since the Camunda Quarkus integration provides a default persistence config it tries to connect with the postgres-driver and a h2 url provided by the Camunda Quarkus integration. Any hints how to get the Quarkus integration running in Dev-Profile with PostgreSQL as a database?

cpbpm · August 17, 2022, 9:22pm

you can check it out here.

github.com

markuspauer/quarkus-camunda-bpm/blob/master/src/main/resources/application.properties

camunda.engine.name = markus
camunda.db.url = jdbc:h2:~/h2/camunda;AUTO_SERVER=TRUE
camunda.db.user = camunda
camunda.db.pass = camunda
#quarkus.http.root-path = /app

joahuber · August 18, 2022, 5:46am

I know how to configure PostgreSQL for the prod-profile where we know the container running the database, but using Quarkus DevServices the url is managed by Quarkus which doesn’t work since Camunda defaults the URL. See Dev Services Overview - Quarkus

system · January 31, 2024, 10:24am