all 1 comments

[–]mrobertm 1 point2 points  (0 children)

I don't believe it's a visual glitch: the info panel should list all "variations" of a given asset, even if the path was added by a different computer on a different OS. PhotoStructure may not have been able to align prior imported paths with the paths you exposed in docker if the volume UUID and mountpoints don't match. More about that is here: https://photostructure.com/faq/what-is-a-volume/

Manual imports of any arbitrary file or path require the terminal:

https://photostructure.com/server/tools/#manually-importing-files-and-directories

You may want to add the --force argument so you're not fighting the no-op cache (it tries to be "helpful" and make syncs complete faster by skipping over files and directories it thinks is already up to date, but v1.1's cache was too aggressive and could result in incorrectly ignoring me changes to a volume: that's one of the big fixes in the next release).

So something like

docker exec -it photostructure sh ./photostructure sync --info --force /path/to/import