forked from zaclys/searxng
3486613a19
A *brand* of searx is a fork which might have its own design and some special functions which might bee reasonable in a special context. In this sense, the fork might have its own documentation but not its own issue tracker. The *upstream* of a brand is always https://github.com/asciimoo from where the brand-fork pulls the master branch regularly. A fork which has its own issue tracker is a spin-off and out of the scope of the searx project itself. The conclusion is: - hard code ISSUE_URL (in the Makefile) - always refer to DOCS_URL - links in the about page refer to the *upstream* (searx project) except DOCS_URL - "fork me on github" ribbons refer to the *upstream* Signed-off-by: Markus Heiser <markus.heiser@darmarit.de> |
||
|---|---|---|
| dockerfiles | ||
| docs | ||
| examples | ||
| searx | ||
| tests | ||
| utils | ||
| .codecov.yml | ||
| .coveragerc | ||
| .dir-locals.el | ||
| .dockerignore | ||
| .gitattributes | ||
| .gitignore | ||
| .landscape.yaml | ||
| .pylintrc | ||
| .travis.yml | ||
| AUTHORS.rst | ||
| CHANGELOG.rst | ||
| Dockerfile | ||
| LICENSE | ||
| Makefile | ||
| 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 of the details, follow this step by step installation.
Note: the documentation needs to be updated.
If you are in a hurry
- clone the 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.pyto start the application
Bugs
Bugs or suggestions? Visit the issue tracker.