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

bitmagnet update #511

Open
wants to merge 6 commits into
base: master
Choose a base branch
from
Open

bitmagnet update #511

wants to merge 6 commits into from

Conversation

rraymondgh
Copy link

Indexer/Tracker

bitmagnet is a self hosted DHT crawler. It provides a torznab standards compliant interface

Current version of bitmagnet.yml cardigan definition ignores all of the extended attributes. Additionally it assumes that bitmagnet is running in same docker daemon or same physical server as Prowlarr.

This change addresses both of those issues. docker daemon / server assumption is a partial fix as cardigan indexers do not support free form definition of URL. This issue has been previously raised Prowlarr/Prowlarr#1892 and rejected. Hence need to go with a long list of locations where bitmagnet maybe hosted in a self hosted setup.

Have also created a PR against bitmagnet to improve use of generic torznab indexer. https://github.com/bitmagnet-io/bitmagnet/pull/369/files This is not well documented in Prowlarr. Have scanned code to conclude comments element is used to generate link to details in indexer.

definitions/v10/bitmagnet.yml Outdated Show resolved Hide resolved
definitions/v10/bitmagnet.yml Outdated Show resolved Hide resolved
definitions/v10/bitmagnet.yml Outdated Show resolved Hide resolved
Comment on lines -78 to -81
downloadvolumefactor:
text: 0
uploadvolumefactor:
text: 1
Copy link
Contributor

@mynameisbogdan mynameisbogdan Jan 18, 2025

Choose a reason for hiding this comment

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

Why remove them?

Copy link
Author

Choose a reason for hiding this comment

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

Why remove them?

aiming at sourcing every attribute from feed. If these attributes do not have defaults and are best provided, they should be reinstated

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