forked from zaclys/searxng
72029d27de
The new url parameter "timeout_limit" set timeout limit defined in second. Example "timeout_limit=1.5" means the timeout limit is 1.5 seconds. In addition, the query can start with <[number] to set the timeout limit. For number between 0 and 99, the unit is the second : Example: "<30 searx" means the timeout limit is 3 seconds For number above 100, the unit is the millisecond: Example: "<850 searx" means the timeout is 850 milliseconds. In addition, there is a new optional setting: outgoing.max_request_timeout. If not set, the user timeout can't go above searx configuration (as before: the max timeout of selected engine for a query). If the value is set, the user can set a timeout between 0 and max_request_timeout using <[number] or timeout_limit query parameter. Related to #1077 Updated version of PR #1413 from @isj-privacore |
||
|---|---|---|
| dockerfiles | ||
| examples | ||
| searx | ||
| tests | ||
| utils | ||
| .codecov.yml | ||
| .coveragerc | ||
| .dockerignore | ||
| .gitattributes | ||
| .gitignore | ||
| .landscape.yaml | ||
| .travis.yml | ||
| AUTHORS.rst | ||
| CHANGELOG.rst | ||
| Dockerfile | ||
| LICENSE | ||
| README.rst | ||
| babel.cfg | ||
| manage.sh | ||
| requirements-dev.txt | ||
| requirements.txt | ||
| setup.py | ||
| tox.ini | ||
README.rst
searx
A privacy-respecting, hackable metasearch engine.
Pronunciation: səːks
List of running instances.
See the documentation and the wiki for more information.
Installation
With Docker ------Go to the searx-docker project.
Without Docker ------For all the details, follow this step by step installation.
Note: the documentation needs to be updated.
If you are in hurry ------- clone source: git clone https://github.com/asciimoo/searx.git && cd searx - install dependencies: ./manage.sh update_packages - edit your settings.yml (set your secret_key!) - run python searx/webapp.py to start the application
Bugs
Bugs or suggestions? Visit the issue tracker.