# +----------------+ # | originalsDir | # +----------------+ # # This is the directory that PhotoStructure uses to store original images when # "copyAssetsToLibrary" is enabled. Absolute paths are supported. Relative # paths are evaluated from your libraryPath. This setting defaults to ".", # which is the same as your PhotoStructure library directory. # # If you open your PhotoStructure library on a different computer, and that # computer doesn't have access to your originals volume, full-screen zoom # won't work, and non-transcoded videos will not play. # # This system setting needs to be set appropriately on different computers (it # won't be set automatically!) # # If you have a large library and want to use an SSD, we recommend you set # your libraryPath to your SSD, and use this setting to store your originals # on a larger volume, rather than using the "previewsDir" setting. # # PS_ORIGINALS_DIR="."
I still have difficulty understanding what the PS library is. Is it the location where my assets are? Is it the location where PS config files and caches live?
originalsDir stores images when “copyAssetsToLibrary” is enabled, but it is separate from
libraryPath stores images, too, right?
If you open your PhotoStructure library on a different computer, and that computer doesn't have access to your originals volume...
If the library is a storage of configs and caches, how can you open it on another computer? Doesn’t it live wherever you are serving PhotoStructure from? And if the library is a storage of your assets, then how can a directory have access to another directory (your originals volume)?
**System settings are specific to a computer.** Examples include what paths to scan, where to save logfiles, and what percent of the CPU can be used during imports.
I’m running PS under Docker, so maybe my understanding of what is/should be where, is biased by this format (or by my limited understanding even of that!). But how does this work? Can I host PS on serverA, and access it via PhotoStructure running on computerB, and separately access it via PhotoStructure running on computerC? If so, can computerB have a settings file saying “scan /mnt/photos” and computerC also have a settings file saying “scan /mnt/photos” but computerB’s /mnt/photos is a different directory than computerC’s /mnt/photos? And if that works, then when I run Photostructure from computerB, will I see the photos that were “imported” into the “library” from computerC’s /mnt/photos
I want to say that your documentation is fabulous, from your questions and explanations on this Forum, to the comments in the settings files, to the support posts on your website. I’m just having trouble understand the concept of the library.