No: I tried to make licensing as transparent as possible–I don’t want to piss off my subscribers!
Once you establish your library with a PLUS license, it should “stick” (and even automatically renew!).
Another user (on UnRAID, not docker) had seen this issue back in September. I made a change (which will be in v2.1, which is not released yet), that should address this bug.
The license file is actually stored in both the library (
$libraryDir/.photostructure/licenses) and in the system configuration directory (
/ps/config/licenses on docker, or
~/.config/PhotoStructure/licenses on linux), so if you use multiple libraries, the second (and Nth) libraries will already have an active license.
PhotoStructure looks at all licenses in both directories and uses the “best” still-current license. You can use
./photostructure info --plan to get details about which license it’s picking, and the details of the license.
In any event, this should all be transparent to you…
Yes: and I only realized the issue that you described after I shipped v1.1.
sync in v2.1 detects if a license is newly activated, and ensures all unique files are properly copied (even if they were synced before with a LITE license).
Yes, but it’s via the command-line. There are a bunch of scenarios with solutions here:
If you have a different question you want me to cook up a script for, please ask: I’m happy to add to that page.
Also: if you want to make sure a specific directory is in sync, you can always shell into your container and run a
docker exec -it name_of_photostructure_container sh
./photostructure sync /path/in/container/to/directory --force --verbose
--force bit tells PhotoStructure not to skip over files that seem like they are in sync already (by looking at the
size of the file).