ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Quarkus Dev Services starts PostgreSQL automatically for local development, but it requires Docker. Learn to configure it and disable it when containers are unavailable.
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.
Learn how to use Quarkus Dev Services to automatically provision database containers during development, eliminating manual setup and ensuring environment consistency.
Learn how Quarkus Dev Services launch disposable containers for integration tests, eliminating manual setup and speeding up feedback loops.
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.
Goal: enable integration tests to use a consistent, non‑production credential set while still letting Quarkus Dev Services manage the lifecycle of a temporary database container. Constraint: Dev Services always generates a new random username and password for each test run and does not expose a way to inject pre‑defined credentials or bind to an external sec
docker
quarkus
java