1
0
Fork 0
mirror of https://github.com/Jackett/Jackett synced 2025-01-03 05:36:44 +00:00

Updated How to request a new tracker (markdown)

garfield69 2021-10-28 20:34:19 +13:00
parent 0c50f560cb
commit 098b6431e9

@ -1,22 +1,13 @@
If you want to request a new tracker, here is the steps to follow : If you want to request a new Indexer for a web site just use the indexer-request issue template [here](https://github.com/Jackett/Jackett/issues/new?template=indexer-request.yml) and fill in the requested details on the form.
##### 1. Create an issue
Please create a new issue [here](https://github.com/Jackett/Jackett/issues/new?template=indexer-request.yml) and prefix it with **[REQ]**
for example: [REQ] ThePirateBay
##### 2. Address to site Notes:
In the body of the ticket provide the full address to the site, eg `https://thepiratebay.org` - If the site is private and subscriptions are closed, we will need an invite to be able to work.
##### 3. Specify site type
identify if the site is:
- _public_ : downloads are available without a registered account
- _semi-private_ : search is available without registration but downloading requires a registered account
- _private_ : a registered account is required to access site.
##### 4. Invite an user
If subscriptions are closed on your tracker, we will need an invite to be able to work.
So please, get an invite and be ready to invite the staff member who will implement it. So please, get an invite and be ready to invite the staff member who will implement it.
If the site has open registration then include this info in the ticket.
##### Additional notes - 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, 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 code an indexer 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 has multiple torrents/magnets under one title, then the indexer will need to be coded in C# - 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#.
- And if the JSON 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.