Skip to content

Make SearXNG use valkey since it is installed#263

Open
mikkotor wants to merge 1 commit intotailscale-dev:mainfrom
mikkotor:valkey-updates-for-searxng-stack
Open

Make SearXNG use valkey since it is installed#263
mikkotor wants to merge 1 commit intotailscale-dev:mainfrom
mikkotor:valkey-updates-for-searxng-stack

Conversation

@mikkotor
Copy link
Copy Markdown

@mikkotor mikkotor commented Apr 11, 2026

Pull Request Title: Make SearXNG use valkey

Description

SearXNG does not use valkey by default. The settings.yml sets the valkey url to false. This PR takes it into use.
It also replaces strings for 'redis' with 'valkey', since this stack is using valkey, not redis

Related Issues

  • None

Type of Change

  • Bug fix
  • New feature
  • Documentation update
  • Refactoring

How Has This Been Tested?

I launched this stack using docker compose up locally and verified valkey is being used by:

  • observing no connection errors from app-searxng container
  • logging into app-searxng and checking SEARXNG_VALKEY_URL is set in env

Checklist

  • I have performed a self-review of my code
  • I have added tests that prove my fix or feature works
  • I have updated necessary documentation (e.g. frontpage README.md)
  • Any dependent changes have been merged and published in downstream modules

Screenshots (if applicable)

None

Additional Notes

None

* Rename redis -> valkey, since Redis is not used here
@mikkotor mikkotor changed the title * Make SearXNG use valkey since it is installed Make SearXNG use valkey since it is installed Apr 11, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant