mirror of
https://github.com/searxng/searxng.git
synced 2026-05-23 11:24:31 +02:00
[mod] drop SearXNG's checker (#5767)
To date, there is no analysis for the checker that could be evaluated in any meaningful way. - https://github.com/searxng/searxng/issues/3407 - https://github.com/searxng/searxng/pull/3312 The checker would need to be completely redesigned, but even then, its usefulness and the maintenance required for it would be disproportionate. TBH: In its current form, it is useless and only consumes resources and causes the engines to be blocked, because these tests (query terms) come from *hundreds* of instances and could be interpreted as bot attacks. Related issues: [search.checker](https://github.com/searxng/searxng/issues?q=label%3A%22search.checker%22) Signed-off-by: Markus Heiser <markus.heiser@darmarit.de>
This commit is contained in:
@@ -39,7 +39,7 @@ setup(
|
||||
],
|
||||
project_urls={"Code": GIT_URL, "Issue tracker": get_setting('brand.issue_url')},
|
||||
entry_points={
|
||||
'console_scripts': ['searxng-run = searx.webapp:run', 'searxng-checker = searx.search.checker.__main__:main']
|
||||
'console_scripts': ['searxng-run = searx.webapp:run']
|
||||
},
|
||||
packages=find_packages(
|
||||
include=[
|
||||
@@ -54,7 +54,6 @@ setup(
|
||||
'settings.yml',
|
||||
'*.toml',
|
||||
'*.msg',
|
||||
'search/checker/scheduler.lua',
|
||||
'data/*.json',
|
||||
'data/*.txt',
|
||||
'data/*.ftz',
|
||||
|
||||
Reference in New Issue
Block a user