.oO SearXNG Developer Documentation Oo.
|
Functions | |
request (query, params) | |
response (resp) | |
Variables | |
dict | about |
list | categories = ['files'] |
bool | paging = True |
bool | time_range_support = True |
str | url = 'https://bt4gprx.com' |
str | search_url = url + '/search?q={search_term}&orderby={order_by}&category={category}&p={pageno}&page=rss' |
str | bt4g_order_by = 'relevance' |
str | bt4g_category = 'all' |
BT4G_ (bt4g.com) is not a tracker and doesn't store any content and only collects torrent metadata (such as file names and file sizes) and a magnet link (torrent identifier). This engine does not parse the HTML page because there is an API in XML (RSS). The RSS feed provides fewer data like amount of seeders/leechers and the files in the torrent file. It's a tradeoff for a "stable" engine as the XML from RSS content will change way less than the HTML page. .. _BT4G: https://bt4g.com/ Configuration ============= The engine has the following additional settings: - :py:obj:`bt4g_order_by` - :py:obj:`bt4g_category` With this options a SearXNG maintainer is able to configure **additional** engines for specific torrent searches. For example a engine to search only for Movies and sort the result list by the count of seeders. .. code:: yaml - name: bt4g.movie engine: bt4g shortcut: bt4gv categories: video bt4g_order_by: seeders bt4g_category: 'movie' Implementations ===============
searx.engines.bt4g.request | ( | query, | |
params ) |
Definition at line 75 of file bt4g.py.
searx.engines.bt4g.response | ( | resp | ) |
Definition at line 90 of file bt4g.py.
dict searx.engines.bt4g.about |
str searx.engines.bt4g.search_url = url + '/search?q={search_term}&orderby={order_by}&category={category}&p={pageno}&page=rss' |