Join our discord community
Attention Proxmox VE Users and native runners
This release adds a searx compatibility layer that allow native searx python engines to run within degoog (read the changelog for more details), that said it means it'll need specific python libraries installed (degoog will tell you when you try to install the engines themselves).
Everything should work fine for you, regardless, the only thing you may not get to enjoy is that compatibility layer until the install script is updated (or you manually install the deps yourself).
Docker image is not affected by this as it'll auto install said deps.
Changelog
Features
- Added a SearX compatibility layer which will allow you to import searxng engines straight from degoog. This will need to be enabled from your server settings. Once enabled navigate to settings -> server to enable it and then navigate to engines, you'll see a new entry to install engines straight from the searxng codebase. This is experimental, I don't plan to maintain the python engines, it's just a way to bridge the two projects for people who like the way searx results are fetched better.
- Added SearxNG compatibility layer for API endpoint too, in order to plug and play degoog instead of searx for deep research with llm (or any other reason you may want your results as searx compatible json format).
- Added chunked index export/import with progress updates and improved modal flows.
- Enhanced search result UI with “recalled” and “indexing/saving” badges and “from-index” messaging.
- Made the engine timing sidebar’s accordion open/closed state responsive to screen width. - Thank you @Panonim
- Updated indexer scoring display with a new “score” column and a configurable “ranking window”.
- Refined extension/settings modal sizing and footer styling for consistency - Thank you @Panonim
- Add new plugin slot location
above-results-full-width - Add ability to enable infinite scroll on results page
Bugfixes
- Improved server restart behavior on Proxmox LXC to avoid unintended process replacement. - Thank you @SoPat712
- Remove insecure --security-opt label=disable flag - Thank you @yeroldsan and @Nick7903
- Update caching to be PER engine rather than overall, this makes it so misses are not expensive on all engines anymore
Security
- Fixed all pending cve from dependencies as always <3
Interesting behind the scene
For anyone curious to know how the whole searx engines work within degoog here's what I came up with
user runs a search
degoog runs the compatibility engine
spawn a python runner which build a faux SearX request
degoog fetches URL through normal engine context like it would for any typescript engine
spawn a python runner that parses response with the SearX response() method
normalize to Degoog results
Degoog is basically leveraging python as if it were running lambdas, which is pretty lightweight, no need to convert anything, having long running processes or acutally running searx. This whole operation adds about 40ms overhead per engine per uncached search, which is a pretty amazing compromise, given the benefits it brings. If you'd rather route searxng via degoog by keeping searxng running as a sidecar instead you can keep the compatibility layer disabled and find the community plugins to do so here clicking on "engines".
