SearXNG Engine for Searching the Community Scripts Catalogue

[ggfevans]

I built a SearXNG engine that lets you search the full community scripts catalogue (~480 scripts) directly from your self-hosted SearXNG instance.

It scratches a specific itch: when fiddling with my Proxmox homelab, I kept asking "is there already an LXC for this?" - now I can do a quick !pve docker or !pve reverse proxy and get an answer without leaving my search page.

I intend to contribute this upstream to the SearXNG project as a built-in engine, but sharing it here for visibility in the meantime.

Screenshot

How it works

• Fetches the full script catalogue from the site's static JSON API, caches locally for 12 hours
• Searches run entirely offline, so your query never leaves your SearXNG instance
• Uses the same scoring algorithm as the community scripts site (+10 name match, +5 description match)
• Results link directly to the script page on community-scripts.github.io
• No extra dependencies beyond SearXNG itself

Install

1. Copy the engine into your SearXNG engines directory
2. Add a 5-line block to settings.yml
3. Restart SearXNG

Works on SearXNG installed via the community scripts LXC. Detailed instructions in the repo.

Repo: https://github.com/ggfevans/SearXNG-Community-Scripts-ProxmoxVE
Licence: AGPL-3.0 (same as SearXNG)

[MickLesk]

Your Image is Broken, but sounds good :D But tbh, i dont know what the "effect" is 😄

[ggfevans]

Whoops, fixed! I had renamed the repo to a more sensible name. Looks like this: https://github.com/ggfevans/SearXNG-Community-Scripts-ProxmoxVE/raw/main/static/screenshot.png

The effect, or intent, was to use SearXNG to help make the Community Scripts catalogue accessible directly.

I also use it in conjunction with a tool I built for Alfred for macOS to integrate SearXNG into that: so now I can search the community catalog right from my desktop. It really just removes a bit of friction in getting to the catalog and so makes it easier to deploy.

[ggfevans]

I also just yesterday updated the script to use SearXNGs native caching and network stack: so its a bit more professional and follows the appropriate patterns of integration. I think I might be able to provide it as an Add-on package, somehow.