docker image does not create/seed sqlite database out of the box about pact_broker-docker HOT 3 CLOSED

Sqlite is only to be used inside the container for demo purposes. There is no production use case for this scenario. Try putting the database in the /tmp directory, as the home directory is probably not writeable for security purposes.

from pact_broker-docker.

thx for your feedback @bethesque

I understand the container is intended for production use and certainly sqlite is not meant to be used in production environments.

please consider also people using this image for evaluation purposes, where sqlite in general is a pretty good choice as it requires way less work for setup und persistence, performance and alike are neglectible when spinning up a container for a quick glance.

If the container is not be used for evaluation or simple out-of-the-box functionality in combination with sqlite it would be advisable to indicate this in the README. Would maybe save some others folks some time spent in debugging/analysis ;)

from pact_broker-docker.

I think most people use the docker-compose file, or mount a directory from a local volume, which is why this hasn't come up before. I've seen your note for an update in the readme, thanks.

from pact_broker-docker.