langgenius/dify
1
0
Fork 0
mirror of https://github.com/langgenius/dify.git synced 2026-08-24 22:11:36 -04:00
Code Issues 775 Packages Projects Releases 10 Wiki Activity

[PR #3363] Integrated SearXNG search as built-in tool #24091

New Issue
Closed
opened 2026-02-21 20:22:21 -05:00 by yindo · 0 comments
yindo commented 2026-02-21 20:22:21 -05:00
Owner
Copy Link
Copy Source

Original Pull Request: https://github.com/langgenius/dify/pull/3363

State: closed
Merged: Yes

Description

Integrated SearXNG search engine as built-in tool. SearXNG is a meta search engine (https://github.com/searxng/searxng) which provides better search results than Google/Bing

Type of Change

  • New feature (non-breaking change which adds functionality)

How Has This Been Tested?

  1. Run SearXNG container
docker run --rm \
             -d -p 8080:8080 \
             -v "${PWD}/searxng:/etc/searxng" \
             -e "BASE_URL=http://0.0.0.0:8080/" \
             -e "INSTANCE_NAME=searxng" \
             searxng/searxng
  1. Add following line in ${PWD}/searxng/settings.yml file
  # remove format to deny access, use lower case.
  # formats: [html, csv, json, rss]
  formats:
    - html
    - json    # <-- add this line
  1. Add SearXNG Search tool
  2. Just like testing the built-in GoogleSearch tool

Suggested Checklist:

  • I have performed a self-review of my own code
  • I have commented my code, particularly in hard-to-understand areas
  • My changes generate no new warnings
  • I ran dev/reformat(backend) and cd web && npx lint-staged(frontend) to appease the lint gods
  • optional I have made corresponding changes to the documentation
  • optional I have added tests that prove my fix is effective or that my feature works
  • optional New and existing unit tests pass locally with my changes
**Original Pull Request:** https://github.com/langgenius/dify/pull/3363 **State:** closed **Merged:** Yes --- # Description Integrated SearXNG search engine as built-in tool. SearXNG is a meta search engine (https://github.com/searxng/searxng) which provides better search results than Google/Bing ## Type of Change - [x] New feature (non-breaking change which adds functionality) # How Has This Been Tested? 1. Run SearXNG container ``` docker run --rm \ -d -p 8080:8080 \ -v "${PWD}/searxng:/etc/searxng" \ -e "BASE_URL=http://0.0.0.0:8080/" \ -e "INSTANCE_NAME=searxng" \ searxng/searxng ``` 2. Add following line in ${PWD}/searxng/settings.yml file ``` # remove format to deny access, use lower case. # formats: [html, csv, json, rss] formats: - html - json # <-- add this line ``` 3. Add SearXNG Search tool 4. Just like testing the built-in GoogleSearch tool # Suggested Checklist: - [x] I have performed a self-review of my own code - [x] I have commented my code, particularly in hard-to-understand areas - [x] My changes generate no new warnings - [ ] I ran `dev/reformat`(backend) and `cd web && npx lint-staged`(frontend) to appease the lint gods - [ ] `optional` I have made corresponding changes to the documentation - [ ] `optional` I have added tests that prove my fix is effective or that my feature works - [ ] `optional` New and existing unit tests pass locally with my changes
yindo added the pull-request label 2026-02-21 20:22:21 -05:00
yindo closed this issue 2026-02-21 20:22:21 -05:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Knowledge Pipeline
Proposal
WIP
cloud
dependencies
feat:webapp
good first issue
outdated
performance
pull-request
Mirrored from GitHub Pull Request
 python:uv
refactor
size:L
stale
status: accepting prs
status: blocked
status: in discussion
stt & tts
vulnerablity
web
wont-fix
🌊 feat:workflow
🌚 invalid
🐞 bug
👻 feat:rag
💪 enhancement
📚 documentation
🔨 feat:tools
🙋‍♂️ question
🙏 help wanted
🤔 cant-reproduce
🤖 feat:agent
No Label pull-request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: langgenius/dify#24091
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?