Insufficient documentation/understanding on env options

[irfanhakim-as]

As per title, I'd like to get more information on these env options:

1. GENERATE_GUIDS
2. GENERATE_LOCATIONS
3. SYNC_FROM_PLEX_TO_JELLYFIN
4. SYNC_FROM_JELLYFIN_TO_PLEX

(1) and (2): What exactly do they do, should only one of them be enabled or can it be both, or neither - and how do I decide which would be best for me according to my setup?

(3) and (4): In general, the sync direction variables - Can multiple/all of them be set to True? or should it only be one of them? For example, is it possible if I enable both of the aforementioned variables, for it to not matter if I watch something on Jellyfin or Plex, and both of those servers will be synced accordingly? or should I only pick one i.e. only sync my watch state from Plex -> Jellyfin, and not be able to have my watchstate on Jellyfin be synced -> Plex simultaneously?

I may have more questions, but it'd be very helpful if I figure these out exactly first. I am in the process of supporting this project in my Helm chart, so it'd be nice if I comprehensively understand these first before implementing these options in my chart. Thank you!

[luigi311]

yes you can enable them all, nothing is exclusive. Most people i would think just leave everything enabled and default.

Generate guids means it will fetch all the media IDs from the providers, IMDB/TVDB, in plex/jellyfin/emby to use for matching.

Generate locations means it will fetch all the file locations/names for the media to use that for matching.

You can use both, getting all the guids is kinda slow so if you are using the exact same storage backend between the media servers then you can disable the guids and use only the file names. This will let it process each loop faster. If the servers are different then you can enable the guids and disable the locations if you want. Or you can just keep both enabled and not worry about it.

[irfanhakim-as]

Thank you, that cleared up most of my questions!

From my understanding, it'd be ideal if we can do away with GENERATE_GUIDS and disable it if possible. Both my servers have their media in the same storage backend (an SMB share) - their file names are identical but their absolute paths atm are different, because they are currently mounted at different locations.

For example:

• Server1: /mnt/media/Movies/Movie/movie.mkv
• Server2: /mymedia/Movies/Movie/movie.mkv

In this instance, does this mean that I should probably rely on and enable GENERATE_GUIDS, rather than GENERATE_LOCATIONS - UNLESS I sort the mount paths and make them identical?

[luigi311]

Generate locations should be fine in this case. It only checks based on the file name itself and not the absolute path since i know most people use docker and absolute paths can change

[irfanhakim-as]

That seems to be what I've found so far too in my testing, I'm super grateful that this neat utility exists. Thanks again for your help and for this amazing project <3