CLARIFICATION: Backup strategy?

Howdy, and welcome the PhotoStructure, @richardjlyon!

My users seem to come from two camps:

  1. They’ve already got their files pretty much entered they want them (and auto organization isn’t a feature they need), or

  2. They’re like me, and have tons of old HDDs filled with backups or main partitions of old servers.

PhotoStructure doesn’t (currently) move files during automatic organization:

I was mostly concerned of the scenario where a user messes up a bind mount for their originals directory within docker, such that those files are only temporarily saved with the container. If I moved files instead of copying, this would result in PhotoStructure effectively deleting the source files during automatic organization because container contents are destroyed when the container image is updated. As far as I know, there isn’t a way to detect this issue (but if anyone knows a solution to this, please share!)

There is a feature request to enable copy-or-move behavior specific to a directory, which I think may be a reasonable solution, as it is evidence that the user read through the documentation at least enough to set up that configuration, but it is months out before I can get to that feature.