Skip to content

qbittorrent and transmission as clients of bitmagnet #301

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

Open
wants to merge 17 commits into
base: main
Choose a base branch
from

Conversation

rraymondgh
Copy link
Contributor

Includes graphql mutation integration. webui is not included as that is subject to change, code is available

Implements interfaces and design constraints noted in issue #300

…l mutation integration. webui is not included as that is subject to change, code is available
@rraymondgh
Copy link
Contributor Author

Tested multiple content types - expected restricted categories work as expected in transmission and qbittorrent

@rraymondgh
Copy link
Contributor Author

client:
  enabled: true
  download_client: QBittorrent
  qbittorrent:
    host: qbittorrent.home
    username: admin
    password: redacted
  transmission:
    host: transmission.home

"uk",
"zh",
]
cmd: npx i18n-auto-translation -k $API_KEY -d webui/src/app/i18n/translations -t {{ .ITEM }}
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not sure how the changes in this file are relevant to the pr

type Config struct {
Enabled bool
Transmission DownloadClient
Qbittorrent DownloadClient
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think I'd prefer a "send to [target]" model with any number of configurable targets possible instead of just 2 hard coded clients.
The "target" wouldn't even have to be a BT client and would allow for more flexibility especially once plugins are possible.

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

Successfully merging this pull request may close these issues.

2 participants