-
Notifications
You must be signed in to change notification settings - Fork 2.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Persist devservices database #30595
Labels
Milestone
Comments
/cc @geoand (devservices), @stuartwdouglas (devservices) |
Sgitario
added a commit
to Sgitario/quarkus
that referenced
this issue
Mar 15, 2023
This is a very useful feature that allows mapping volumes in the Dev Service containers. For example: to keep the Postgres data folder in the localsystem and hence have the data persistently. Fix quarkusio#30595
Sgitario
added a commit
to Sgitario/quarkus
that referenced
this issue
Mar 17, 2023
This is a very useful feature that allows mapping volumes in the Dev Service containers. For example: to keep the Postgres data folder in the localsystem and hence have the data persistently. Fix quarkusio#30595
Sgitario
added a commit
to Sgitario/quarkus
that referenced
this issue
Mar 17, 2023
This is a very useful feature that allows mapping volumes in the Dev Service containers. For example: to keep the Postgres data folder in the localsystem and hence have the data persistently. Fix quarkusio#30595 Co-authored-by: Yoann Rodière <[email protected]>
Sgitario
added a commit
to Sgitario/quarkus
that referenced
this issue
Mar 21, 2023
This is a very useful feature that allows mapping volumes in the Dev Service containers. For example: to keep the Postgres data folder in the localsystem and hence have the data persistently. Fix quarkusio#30595 Co-authored-by: Yoann Rodière <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Description
Currently there isn't anything provided by Quarkus that allows to persist Quarkus devservices databases. We have needs of developing using a database that is going to have a lot of migrations and potentially lot of data, which may become cumbersome if database container is spin, migrated and populated every time the application starts.
We could simply not use devservices but in any case wouldn't be useful to have a way of using Docker volumes for devservices database?
Implementation ideas
Maybe a way of using volumes could be a property
quarkus.datasource.devservices.volume=some_volume
that will reusesome_volume
existing volume with the spin Docker container.The text was updated successfully, but these errors were encountered: