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

Add Plugin structure #1568

Open
labrys opened this issue Mar 10, 2019 · 2 comments
Open

Add Plugin structure #1568

labrys opened this issue Mar 10, 2019 · 2 comments

Comments

@labrys
Copy link
Collaborator

labrys commented Mar 10, 2019

nzbToMedia can be used with a variety of downloaders (e.g. uTorrent, SABnzbd, etc) and media managers (e.g. SickBeard, Radarr, etc) and other utilities for optional functionality (e.g. transcoding, notifications, subtitles, etc). This leads to a large variation in possible configurations.

A plugin structure would separate the code into logical sections to facilitate troubleshooting issues, unit testing, and add-on development.

Additionally if plugins were loaded based only when needed, it would improve stability (bugs in other areas would not affect operation) and efficiency.

@clinton-hall
Copy link
Owner

Yes, I agree.
Starting as a simple "CouchPotato" equivalent of sabToScikBeard, this script has just had more and more options added to it, with more downloaders, media managers, and features added.

So with a plugin structure, we would have:

  • Plugins for each Downloader (input)
  • Plugins for Transcoding, Media Checking, Safe-renaming, linking etc
  • Plugins for each media Manager (output)

is that what you are thinking, or do you have another thought as to how these would be sectioned out?

@labrys
Copy link
Collaborator Author

labrys commented Mar 10, 2019

That's pretty much it in a nutshell

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants