forked from zaclys/searxng
cdc2f33972
This is a second proposal to accomplish plugin decoupling. I think #1938 is highly complicated and does much more than this feature requires, so here is an alternative implementation for the same feature. Please review it and let me know your opinion. This solution supports the use of any kind of standard python modules which implements the required attributes of a plugin, so new plugins can be installed by standard python tools (pip/setup.py). Downsides: - Localization of plugins name/description isn't possible - Plugins have to be updated manually ## What does this PR do? Implements external plugin extensibility. ## Why is this change important? Makes us able to decouple plugins from searx. ## Related issues #1938 #1716 #1878 |
||
---|---|---|
dockerfiles | ||
docs | ||
examples | ||
searx | ||
tests | ||
utils | ||
.codecov.yml | ||
.config.sh | ||
.coveragerc | ||
.dir-locals.el | ||
.dockerignore | ||
.gitattributes | ||
.gitignore | ||
.landscape.yaml | ||
.pylintrc | ||
.travis.yml | ||
AUTHORS.rst | ||
CHANGELOG.rst | ||
CONTRIBUTING.md | ||
Dockerfile | ||
LICENSE | ||
Makefile | ||
PULL_REQUEST_TEMPLATE.md | ||
README.rst | ||
babel.cfg | ||
manage.sh | ||
requirements-dev.txt | ||
requirements.txt | ||
setup.py | ||
tox.ini |
README.rst
Privacy-respecting, hackable metasearch engine / pronunciation səːks.
If you are looking for running instances, ready to use, then visit searx.space.
Otherwise jump to the user, admin and developer handbooks you will find on our homepage.