use separate docker-compose projects for tests and local dev databases #1690
Labels
effort/hours
Estimated to take one or several hours
kind/enhancement
A net-new feature or improvement to an existing feature
kind/maintenance
Work required to avoid breaking changes or harm to project's status quo
pi/support-0
status/ready
Ready to be worked
topic/devexp
Developer Experience
The current docker-compose setup for testing and local development supports two use cases that have a lot of overlapping functionality: running unit / integration tests, and manually poking at things during iterative development.
The first use case wants a clean slate for each run, while the second benefits from a persistent data store so you can make small changes and see their effects while developing.
All the docker containers for the database setup are tagged with a docker-compose project name, so we could use a second project name for each use case. Then we can always reset / clear the "testing" project after each run, but leave the "debug" project alone and let the developer manually clear it when they need to.
The text was updated successfully, but these errors were encountered: