Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merge plex_library_sync.py into plex_sync.py #207

Open
Casvt opened this issue Apr 16, 2024 · 0 comments
Open

Merge plex_library_sync.py into plex_sync.py #207

Casvt opened this issue Apr 16, 2024 · 0 comments
Labels
1. Feature request Request for feature to be added to script 2. Level: Hard The request is a good challenge 3. Request accepted Request is accepted and will be realised

Comments

@Casvt
Copy link
Owner

Casvt commented Apr 16, 2024

In what file should the feature be added?

plex_sync.py

What is the feature request?

plex_library_sync.py can be seen as syncing two libraries on the same server. So in order to make this work, a few things need to be added to the plex_sync.py script:

  1. Better target selection. Instead of syncing the whole server, there needs to be options to only sync a certain library, or even specific media only. This way you can specify to only sync a certain library
  2. If needed, allow the source and target server to be the same server. Add optimisations that can be made if they are the same, e.g. only fetching library data once and save it as both the source and target data.
  3. Allow manual overriding of the library mapping. Currently, libraries are said to be the same on two servers if they're for the same media type and if they have the same name. Allow to override this, so that the user can specify that "Movies" and "Movies (Kids only)" are the "same" library on the same server.
  4. Add any handling for if the media is not found.
@Casvt Casvt added the 1. Feature request Request for feature to be added to script label Apr 16, 2024
Casvt added a commit that referenced this issue Apr 16, 2024
@Casvt Casvt added 2. Level: Hard The request is a good challenge 3. Request accepted Request is accepted and will be realised labels May 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
1. Feature request Request for feature to be added to script 2. Level: Hard The request is a good challenge 3. Request accepted Request is accepted and will be realised
Projects
None yet
Development

No branches or pull requests

1 participant