installation-scripts.rst 1.9 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263
  1. .. _installation scripts:
  2. ===================
  3. Installation Script
  4. ===================
  5. .. sidebar:: Update the OS first!
  6. To avoid unwanted side effects, update your OS before installing SearXNG.
  7. The following will install a setup as shown in :ref:`the reference architecture
  8. <arch public>`. First you need to get a clone of the repository. The clone is only needed for
  9. the installation procedure and some maintenance tasks.
  10. .. sidebar:: further read
  11. - :ref:`toolboxing`
  12. Jump to a folder that is readable by *others* and start to clone SearXNG,
  13. alternatively you can create your own fork and clone from there.
  14. .. code:: bash
  15. $ cd ~/Downloads
  16. $ git clone https://github.com/searxng/searxng.git searxng
  17. $ cd searxng
  18. .. sidebar:: further read
  19. - :ref:`inspect searxng`
  20. To install a SearXNG :ref:`reference setup <use_default_settings.yml>`
  21. including a :ref:`uWSGI setup <architecture uWSGI>` as described in the
  22. :ref:`installation basic` and in the :ref:`searxng uwsgi` section type:
  23. .. code:: bash
  24. $ sudo -H ./utils/searxng.sh install all
  25. .. attention::
  26. For the installation procedure, use a *sudoer* login to run the scripts. If
  27. you install from ``root``, take into account that the scripts are creating a
  28. ``searxng`` user. In the installation procedure this new created user does
  29. need to have read access to the cloned SearXNG repository, which is not the case if you clone
  30. it into a folder below ``/root``!
  31. .. sidebar:: further read
  32. - :ref:`update searxng`
  33. .. _caddy: https://hub.docker.com/_/caddy
  34. When all services are installed and running fine, you can add SearXNG to your
  35. HTTP server. We do not have any preferences regarding the HTTP server, you can use
  36. whatever you prefer.
  37. We use caddy in our :ref:`docker image <installation docker>` and we have
  38. implemented installation procedures for:
  39. - :ref:`installation nginx`
  40. - :ref:`installation apache`