Closed 8ryn closed 1 year ago
By default the mongoDB docker container creates a new docker volume each time it is instantiated, these volumes have randomly generated names. This means that each time the docker compose environment is restarted the data from previous runs is not reloaded.
Aha, so that doesn't explain my problems using the mongodb backend for bluesky databroker... hmm 🤔
This PR simply adds an explicit named docker volume to the docker compose file which means that previous data will be accessible even when the mongoDB container is restarted.
Good addition. That will probably save a bit of time when restarting AND you can carry on from yesterday's work with more scans available in the databroker. Just do a docker volume rm tomoscan_mongodbdata
before starting if you need a clean slate...
By default the mongoDB docker container creates a new docker volume each time it is instantiated, these volumes have randomly generated names. This means that each time the docker compose environment is restarted the data from previous runs is not reloaded.
This PR simply adds an explicit named docker volume to the docker compose file which means that previous data will be accessible even when the mongoDB container is restarted.