searxng/utils/searxng.sh, branch custom

[fix] installation instructions - launch SearXNG by python -m (#6078)

2026-05-13T09:34:31Z

[1] https://github.com/searxng/searxng/issues/126#issuecomment-4433874986 Suggested-by: @virtadpt in [1]

[doc] add missing packages required for installation (#5951)

2026-04-04T17:02:44Z

Related: - https://github.com/searxng/searxng/pull/5763 - https://github.com/searxng/searxng/pull/5765 - https://github.com/searxng/searxng/pull/5346 Closes: https://github.com/searxng/searxng/issues/5937 Signed-off-by: Markus Heiser

[fix] searxng.sh fails: No module named 'pybind11' (#5765)

2026-02-22T09:23:59Z

Related: https://github.com/searxng/searxng/discussions/5748#discussioncomment-15880660 Signed-off-by: Markus Heiser

[fix] searxng.sh fails: No module named 'typing_extensions'

2026-02-21T12:41:52Z

Closes: #5761 Signed-off-by: Markus Heiser

[fix] Installation Script install fails (msgspec) (#5358)

2025-10-23T07:27:14Z

Since #5280 has been merged, msgspec, like yaml, is a fixed part of the SearXNG *settings framework* and therefore, like yaml, must be installed in the virtual environment before installing SearXNG (``searx``). The actual reason is that in SearXNG we store settings in the configuration that are required for the installation of the ``searx`` package. This means that these settings (from settings.yml) are read in during the installation, and all the necessary tools for this (pyyaml, msgspec, setuptools, etc.) must be installed beforehand (chicken or the egg dilemma). Related: - https://github.com/searxng/searxng/pull/5353 - https://github.com/searxng/searxng/pull/5346 - https://github.com/searxng/searxng/pull/5280 - https://github.com/searxng/searxng/pull/5254 Closes: https://github.com/searxng/searxng/issues/5357 Signed-off-by: Markus Heiser

[fix] Installation Script install fails (msgspec) (#5346)

2025-10-20T09:21:48Z

Since #5280 has been merged, msgspec, like yaml, is a fixed part of the SearXNG *settings framework* and therefore, like yaml, must be installed in the virtual environment before installing SearXNG (``searx``). The actual reason is that in SearXNG we store settings in the configuration that are required for the installation of the ``searx`` package. This means that these settings (from settings.yml) are read in during the installation, and all the necessary tools for this (pyyaml, msgspec, setuptools, etc.) must be installed beforehand (chicken or the egg dilemma). Related: - https://github.com/searxng/searxng/pull/5280 - https://github.com/searxng/searxng/pull/5254 Closes: https://github.com/searxng/searxng/issues/5343 Signed-off-by: Markus Heiser

[fix] apply shell formating / shfmt (make format.shell)

2025-07-28T10:53:26Z

Signed-off-by: Markus Heiser

[chore] overdue maintenance of shell scripts

2025-07-28T10:53:26Z

Removes obsolete scripts and fix various leftovers. Signed-off-by: Markus Heiser

[mod] migrate from Redis to Valkey (#4795)

2025-07-09T05:55:37Z

This patch migrates from `redis==5.2.1` [1] to `valkey==6.1.0` [2]. The migration to valkey is necessary because the company behind Redis has decided to abandon the open source license. After experiencing a drop in user numbers, they now want to run it under a dual license again. But this move demonstrates once again how unreliable the company is and how it treats open source developers. To review first, read the docs:: $ make docs.live Follow the instructions to remove redis: - http://0.0.0.0:8000/admin/settings/settings_redis.html Config and install a local valkey DB: - http://0.0.0.0:8000/admin/settings/settings_valkey.html [1] https://pypi.org/project/redis/ [2] https://pypi.org/project/valkey/ Co-authored-by: HLFH Co-authored-by: Markus Heiser

[fix] debian: install apt package python-is-python3

2025-06-25T06:29:57Z

On debian the 'python-is-python3' packages restores an appropriate '/usr/bin/python' symlink for third-party scripts[1] [1] https://github.com/searxng/searxng/issues/3235#issuecomment-1954459081 Signed-off-by: Markus Heiser