summaryrefslogtreecommitdiff
path: root/_sources/dev/engines/offline/search-indexer-engines.rst.txt
blob: fa92798cb5926c23514752486f740929883680ca (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
=================
Local Search APIs
=================

.. sidebar:: further read

   - `Comparison to alternatives
     <https://docs.meilisearch.com/learn/what_is_meilisearch/comparison_to_alternatives.html>`_

.. contents::
   :depth: 1
   :local:
   :backlinks: entry

.. sidebar:: info

   Initial sponsored by `Search and Discovery Fund
   <https://nlnet.nl/discovery>`_ of `NLnet Foundation <https://nlnet.nl/>`_.

Administrators might find themselves wanting to integrate locally running search
engines.  The following ones are supported for now:

* `Elasticsearch`_
* `Meilisearch`_
* `Solr`_

Each search engine is powerful, capable of full-text search.  All of the engines
above are added to ``settings.yml`` just commented out, as you have to
``base_url`` for all them.

Please note that if you are not using HTTPS to access these engines, you have to
enable HTTP requests by setting ``enable_http`` to ``True``.

Furthermore, if you do not want to expose these engines on a public instance,
you can still add them and limit the access by setting ``tokens`` as described
in section :ref:`private engines`.

.. _engine meilisearch:

MeiliSearch
===========

.. automodule:: searx.engines.meilisearch
  :members:


.. _engine elasticsearch:

Elasticsearch
=============

.. automodule:: searx.engines.elasticsearch
  :members:

.. _engine solr:

Solr
====

.. automodule:: searx.engines.solr
  :members: