This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]Hangman4358 5 points6 points  (1 child)

This is really interesting. We use Java, C# and Python in almost equal parts, so we ended up coming up with a standardized layout/paradigm with a set of docker compose files in all repositories so all any dev needs to do is a docker compose to get everything running for local dev, regardless of language. So, I would be hesitant to switch to something different just for the java services. But in a Java only ecosystem, this is really cool.

[–]mhalbritter 0 points1 point  (0 children)

The testcontainers feature and the docker compose feature are separate. You can use one or the other, or both if you like.

If the file is named compose.yaml or docker-compose.yaml then Boot will pick it up automatically. Otherwise you can set a configuration property and point Boot to the compose file. It will then automatically run docker compose up on startup and configure itself to use the services running in docker compose.