Index: Ignore nested storage folder in the originals path

[oscadev]

RIght now, if a user places their "Storage" folder (the folder where albums, sidecar, config, cache etc are) inside their "pictures" folder *the folder that it scans to index from), it creates a loop where it creates thumbnails in Storage, indexes the thumbnails, then makes thumbnails of the thumbnail images, index those etc in a recursive loop.

A potential solution is to write a .dont-scan-me file in the storage folder which tells Photoprism to skip it when indexing.

[lastzero]

That's in fact a supported config IF you use a hidden folder name like .photoprism or add the name to a .ppignore file. Should be able to detect this specific edge case though and then also ignore it. Can't change your container config from inside the container. Only option would be to error on startup otherwise.

[svengreb]

I'd vote for the fail-fast solution here to error on startup. Even though it can be avoid by setting up ignore pattern, this is a case where I see responsibility on the side of the application. Without looking into the code I guess the configurations should be available to the application on startup and therefore allows to check whether the storage path is a sub-directory of the import/originals directory. If so deny to start with the reason of invalid configuration(s).

[lastzero]

It's really not THAT easy because Docker hides the actual host paths. The storage folder could be ANYWHERE in originals. Can't check all folders in originals on startup.

[graciousgrey]

An onboarding wizard for setting config values like paths and the admin password using the web ui is planned as well. It will include at least a hint to not put the storage insides of originals.

[srett]

It's really not THAT easy because Docker hides the actual host paths. The storage folder could be ANYWHERE in originals. Can't check all folders in originals on startup.

I think if it's supposed to be a supported configuration, creating a special marker-file a la .dont-scan-me in the storage folder is the most pragmatic solution. Create it on startup, if this fails error out immediately. Then when scanning, don't descend into any directory that contains said flag file.
The only way to break things then would be if the user deliberately deletes the flag after startup, but you can only do so much to protect a user from themselves. ;-)

[svengreb]

It's really not THAT easy because Docker hides the actual host paths. The storage folder could be ANYWHERE in originals. Can't check all folders in originals on startup.

Right, I haven't take the container <-> host mapping into account, but @srett already posted the next idea I had 😄
Always creating a .ppignore file in the storage directory on startup should cover 99,9% of all use cases. When someone deletes the file during runtime this is definitely an action that was forced by the user. I guess the file should also include a comment that informs about the purpose of the file and the consequences when it gets deleted.

[lastzero]

Sounds perfect 👍

[lastzero]

Updated the Known Issues page in our docs to include this issue:

• photoprism/photoprism-docs@23282f0

Published: https://docs.photoprism.app/known-issues/#nested-storage-folder