i was rebooting my proxmox machine and the vm photoprism is running on didnt have the mnts configured correctly on boot. so when photoprism docker spun up the folders from the nas werent mnt and photoprism assumed them to be empty i think. i didnt realize early enough, it all went so fast. and once i relaized photoprism library was empty bascially
so after i spun down the docker, properly mounted my nas on the photoprism vm and restarted the photoprism docker again i did a library rescan. folders turned up again.
but now ALL my archived images are not archived anymore. is that by design?
that feels like a bug to me. i spent literal hours putting 1-2k pictures in the archive that i dont want in my photoprism library. now i have to do that all over again?
is there an option to disallow photoprism completely from kicking images it cant find from the library without asking first? it all went so fast, suddenly the whole library was empty.
i was rebooting my proxmox machine and the vm photoprism is running on didnt have the mnts configured correctly on boot. so when photoprism docker spun up the folders from the nas werent mnt and photoprism assumed them to be empty i think. i didnt realize early enough, it all went so fast. and once i relaized photoprism library was empty bascially
so after i spun down the docker, properly mounted my nas on the photoprism vm and restarted the photoprism docker again i did a library rescan. folders turned up again.
but now ALL my archived images are not archived anymore. is that by design?
that feels like a bug to me. i spent literal hours putting 1-2k pictures in the archive that i dont want in my photoprism library. now i have to do that all over again?
is there an option to disallow photoprism completely from kicking images it cant find from the library without asking first? it all went so fast, suddenly the whole library was empty.