Photoprism: docker: document where scan results are stored
Using the default docker setup, I want to avoid re-scanning after upgrading the docker container. I would also like to avoid re-scanning the same image if it has not changed.
Currently the docs do not make clear how scanning is done or scan results are persisted.
andig
>All comments
Yes, the image is mainly there for testing and the demo. You need a persistent file system to keep the database. If you check our docker-compose.yml file, you see the various environment variables you can (you can also do this with a config file which should be documented in our wiki):
https://github.com/photoprism/photoprism/blob/develop/docker-compose.yml
Update: Note that the default paths are different in our production image, but you can set the variables to whatever you want anyways (make sure to mount an external, persistent file system in that location).
lastzero
on 11 Sep 2019
Related issues
lastzero
路
4Comments
Toothwitch
路
4Comments
wiwie
路
3Comments
twatzl
路
4Comments
lastzero
路
3Comments
Most helpful comment
Yes, the image is mainly there for testing and the demo. You need a persistent file system to keep the database. If you check our docker-compose.yml file, you see the various environment variables you can (you can also do this with a config file which should be documented in our wiki):
https://github.com/photoprism/photoprism/blob/develop/docker-compose.yml
Update: Note that the default paths are different in our production image, but you can set the variables to whatever you want anyways (make sure to mount an external, persistent file system in that location).