1
0
Fork 0
mirror of https://github.com/Jackett/Jackett synced 2024-12-22 15:57:50 +00:00

Updated How to request a new tracker (markdown)

garfield69 2022-04-24 18:13:08 +12:00
parent da5dc59c67
commit 6372a99f98

@ -6,8 +6,8 @@ So please, get an invite and be ready to invite the staff member who will implem
If the site has open registration then include this info in the ticket. If the site has open registration then include this info in the ticket.
- The site must provide .torrent or magnet or both. Sites that only provide direct downloads to browser, or direct play/view, or redirection links to file storage sites are not suitable for use with Jackett. - The site must provide .torrent or magnet or both. Sites that only provide direct downloads to browser, or direct play/view, or redirection links to file storage sites are not suitable for use with Jackett.
- If the site has one title for each torrent/magnet then we can usually code an indexer in yaml using the Cardigann processor. - If the site has one title for each torrent/magnet then we can usually code an indexer in yaml using the Cardigann processor.
- If the site uses an API that returns JSON then in most cases we can also write the indexer in yaml. - If the site uses an API that returns JSON or XML then in most cases we can also write the indexer in yaml.
- Yaml indexers are simple to write and maintain, and usually the turn around from request to implementation is fairly short. - Yaml indexers are simple to write and maintain, and usually the turn around from request to implementation is fairly short.
- If the site has multiple torrents/magnets under one title, then the indexer will need to be coded in C#. - If the site has multiple torrents/magnets under one title, then the indexer will need to be coded in C#.
- And if the JSON api returns very complex results that cannot be process with yaml, then we will need to resort to C#. - And if the JSON/XML api returns very complex results that cannot be process with yaml, then we will need to resort to C#.
- C# indexers do not have a quick turn around from request to implementation, usually due to the fact that C# developers are scarce or busy on other projects. - C# indexers do not have a quick turn around from request to implementation, due to the fact that C# developers are scarce and/or busy on other projects.