This came up in the Discord chat a while ago… this seems like a good place to pick up the discussion.
In order to provide the optimal setup for Unraid, we need to be clear about all of the different paths that Photostructure has. I’m going to attempt to outline that here. @mrm feel free to edit anything that I don’t have quite right.
Library Path (/ps/Library) - This always holds the Photostructure database and image preview files, and also by default holds your auto-organized photos/videos (if that setting is enabled). This path is also always included as a source of images, and will be scanned when sync is run. Default template path: mnt/user/Photos (note: I think this is not a great default since it assumes that the user created a “Photos” user share)
Temp Path (/ps/tmp) - This holds temporary files that Photostructure creates during normal operation. Default template path: /mnt/user/appdata/photostructure/tmp
Config Path (/ps/config) - This holds configuration files like the settings.toml file. Default template path: /mnt/user/appdata/photostructure/config
Logs Path (/ps/logs) - This holds log files generated by Photostructure. Default template path: /mnt/user/appdata/photostructure/logs
Originals Directory (set by PS_ORIGINALS_DIR evnironment variable) - Auto-organization by default saves files to the Library path. You can override this by specifying a different path in the PS_ORIGINALS_DIR environment variable. This is preferable if you want your library database/previews on your SSD cache (which will improve performance), but save your asset files on your Unraid array.
Source Location - Chances are, your asset files already have a home on Unraid. You need to add a path to your Docker setup to allow the Photostructure container to access your files.