2016-07-15 16:41:05 +00:00
|
|
|
.. _installation:
|
|
|
|
|
|
2019-12-04 16:54:41 +00:00
|
|
|
============
|
2015-11-17 22:13:30 +00:00
|
|
|
Installation
|
|
|
|
|
============
|
|
|
|
|
|
2020-03-02 18:00:19 +00:00
|
|
|
*You're spoilt for choice*, choose your preferred method of installation.
|
2020-02-04 15:42:13 +00:00
|
|
|
|
2020-03-02 18:00:19 +00:00
|
|
|
- :ref:`installation docker`
|
2020-03-04 18:56:40 +00:00
|
|
|
- :ref:`installation scripts`
|
2020-03-02 18:00:19 +00:00
|
|
|
- :ref:`installation basic`
|
2020-02-04 15:42:13 +00:00
|
|
|
|
2020-03-02 18:00:19 +00:00
|
|
|
The :ref:`installation basic` is good enough for intranet usage and it is a
|
|
|
|
|
excellent illustration of *how a searx instance is build up*. If you place your
|
|
|
|
|
instance public to the internet you should really consider to install a
|
|
|
|
|
:ref:`filtron reverse proxy <filtron.sh>` and for privacy a :ref:`result proxy
|
|
|
|
|
<morty.sh>` is mandatory.
|
2020-02-04 15:42:13 +00:00
|
|
|
|
2020-03-02 18:00:19 +00:00
|
|
|
Therefore, if you do not have any special preferences, its recommend to use the
|
|
|
|
|
:ref:`installation docker` or the `Installation scripts`_ from our :ref:`tooling
|
|
|
|
|
box <toolboxing>` as described below.
|
2016-01-10 19:10:53 +00:00
|
|
|
|
2020-03-04 18:56:40 +00:00
|
|
|
.. _installation scripts:
|
2020-02-04 12:13:17 +00:00
|
|
|
|
2020-03-02 18:00:19 +00:00
|
|
|
Installation scripts
|
|
|
|
|
====================
|
2015-11-17 22:13:30 +00:00
|
|
|
|
2020-04-28 12:44:28 +00:00
|
|
|
.. sidebar:: Update OS first!
|
|
|
|
|
|
|
|
|
|
To avoid unwanted side effects, update your OS before installing searx.
|
|
|
|
|
|
2020-03-02 18:00:19 +00:00
|
|
|
The following will install a setup as shown in :ref:`architecture`. First you
|
|
|
|
|
need to get a clone. The clone is only needed for the installation procedure
|
|
|
|
|
and some maintenance tasks (alternatively you can create your own fork).
|
2020-02-04 12:13:17 +00:00
|
|
|
|
2020-12-13 14:19:04 +00:00
|
|
|
For the installation procedure, use a *sudoer* login to run the scripts. If you
|
|
|
|
|
install from ``root``, take into account that the scripts are creating a
|
|
|
|
|
``searx``, a ``filtron`` and a ``morty`` user. In the installation procedure
|
|
|
|
|
these new created users do need read access to the clone of searx, which is not
|
|
|
|
|
the case if you clone into a folder below ``/root``.
|
|
|
|
|
|
|
|
|
|
|
2020-03-02 18:00:19 +00:00
|
|
|
.. code:: bash
|
2020-02-04 12:13:17 +00:00
|
|
|
|
2020-04-09 13:04:23 +00:00
|
|
|
$ cd ~/Downloads
|
2020-09-28 14:44:14 +00:00
|
|
|
$ git clone https://github.com/searx/searx searx
|
2020-03-02 18:00:19 +00:00
|
|
|
$ cd searx
|
2015-11-17 22:13:30 +00:00
|
|
|
|
2020-03-02 18:00:19 +00:00
|
|
|
**Install** :ref:`searx service <searx.sh>`
|
2015-11-17 22:13:30 +00:00
|
|
|
|
2020-03-02 18:00:19 +00:00
|
|
|
This installs searx as described in :ref:`installation basic`.
|
2015-11-17 22:13:30 +00:00
|
|
|
|
2020-03-02 18:00:19 +00:00
|
|
|
.. code:: bash
|
2015-11-17 22:13:30 +00:00
|
|
|
|
2020-03-02 18:00:19 +00:00
|
|
|
$ sudo -H ./utils/searx.sh install all
|
2015-11-17 22:13:30 +00:00
|
|
|
|
2020-03-02 18:00:19 +00:00
|
|
|
**Install** :ref:`filtron reverse proxy <filtron.sh>`
|
2020-02-04 15:42:13 +00:00
|
|
|
|
2020-03-02 18:00:19 +00:00
|
|
|
.. code:: bash
|
2019-12-04 16:54:41 +00:00
|
|
|
|
2020-03-02 18:00:19 +00:00
|
|
|
$ sudo -H ./utils/filtron.sh install all
|
2019-12-04 16:54:41 +00:00
|
|
|
|
2020-03-02 18:00:19 +00:00
|
|
|
**Install** :ref:`result proxy <morty.sh>`
|
2015-11-17 22:13:30 +00:00
|
|
|
|
2020-03-02 18:00:19 +00:00
|
|
|
.. code:: bash
|
2015-11-17 22:13:30 +00:00
|
|
|
|
2020-03-02 18:00:19 +00:00
|
|
|
$ sudo -H ./utils/morty.sh install all
|
2020-04-06 15:59:06 +00:00
|
|
|
|
|
|
|
|
If all services are running fine, you can add it to your HTTP server:
|
|
|
|
|
|
|
|
|
|
- :ref:`installation apache`
|
|
|
|
|
- :ref:`installation nginx`
|
|
|
|
|
|
2020-12-13 14:20:33 +00:00
|
|
|
.. _git stash: https://git-scm.com/docs/git-stash
|
|
|
|
|
|
|
|
|
|
.. tip::
|
|
|
|
|
|
|
|
|
|
About script's installation options have a look at chapter :ref:`toolboxing
|
|
|
|
|
setup`. How to brand your instance see chapter :ref:`makefile setup`. To
|
|
|
|
|
*stash* your instance's setup, `git stash`_ your clone's :origin:`Makefile`
|
|
|
|
|
and :origin:`.config.sh` file .
|
