Implementing Local Data Persistence with Quarkus Dev Services for PostgreSQL
Learn how to use Quarkus Dev Services to automatically provision PostgreSQL containers for local development, eliminating manual database setup and configuration friction.
ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Learn how to use Quarkus Dev Services to automatically provision PostgreSQL containers for local development, eliminating manual database setup and configuration friction.
Quarkus Dev Services can start a PostgreSQL container automatically in dev and test mode, eliminating manual database setup. Learn the prerequisites, configuration, and verification steps.
When writing integration tests for a Kotlin‑based Spring Boot application, the goal is to validate data‑access logic without requiring production database credentials. The Spring Boot @DataJpaTest slice automatically configures an in‑memory H2 database, which satisfies the credential‑free requirement but may not fully emulate the behavior of a production Pos
Quarkus Dev Services start a PostgreSQL container automatically when your datasource has no URL — no Testcontainers boilerplate in dev mode or tests. Here's how it works, how to customize it, and where it breaks.
I've been successfully using TestContainers with Docker for quite a while now. All of a sudden today, I started getting this error: UnixSocketClientProviderStrategy: failed with exception BadRequestException (Status 400: {"message":"client version 1.32 is too old. Minimum supported API version is 1.44, please upgrade your client to a newer version"} What cou