4 commits

Author	SHA1	Message	Date
HLFH	36538e6a20	[mod] migrate from Redis to Valkey ... 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: Markus Heiser <markus.heiser@darmarit.de>	2025-07-08 13:10:13 +02:00
Leo Liu	b173f3a8b9	Fix scheduler.lua	2024-11-10 15:53:58 +01:00
Alexandre FLAMENT	e92755d358	Initialize Redis in searx/webapp.py ... settings.yml: * The default URL was unix:///usr/local/searxng-redis/run/redis.sock?db=0 * The default URL is now "false" The default URL makes the log difficult to deal with: if the admin didn't install a Redis instance, the logs record a false error. It worked before because SearXNG initialized the Redis connection when the limiter started. In this commit, SearXNG initializes Redis in searx/webapp.py so various components can use Redis without taking care of the initialization step.	2022-11-05 17:45:52 +01:00
Alexandre Flament	fe419e355b	The checker requires Redis ... Remove the abstraction in searx.shared.SharedDict. Implement a basic and dedicated scheduler for the checker using a Redis script.	2022-11-05 12:04:50 +01:00