Chris wrote:
Before creating that file, let's verify that your installed SearXNG setup actually mounts that state path as its settings file; otherwise it may be ignored, and editing the shipped config could be overwritten. What SparkBox version is installed, and is this SearXNG instance the standard SparkBox install? Please don't paste either settings file or any secrets.
Chris wrote:
Following up with the answer, since it's the same on every version: you don't need a second file. The file you're worried about is already yours. SparkBox doesn't ship a SearXNG settings.yml at all. SearXNG writes modules/searxng/config/settings.yml itself the first time it starts. sudo sparkbox upgrade carries that whole config folder over untouched, like every app's config folder, so your edits there survive updates and nothing of ours overwrites them. A file under state/searxng/ wouldn't work, because SearXNG only reads its own config folder. If you want your changes kept apart from SearXNG's defaults, SearXNG has that built in: 1. Keep a copy first: sudo cp /opt/sparkbox/modules/searxng/config/settings.yml /opt/sparkbox/modules/searxng/config/settings.yml.orig (use your own SparkBox folder if it isn't /opt/sparkbox). 2. Replace settings.yml with a short file whose first line is usedefaultsettings: true, followed only by the settings you change. Everything you leave out comes from SearXNG's own built-in defaults, including new ones when SearXNG updates. Leave secretkey out; SparkBox already hands SearXNG its key. 3. sudo sparkbox restart searxng If the search page doesn't come back after the restart, copy settings.yml.orig back over settings.yml and restart again. Your old file is untouched in that copy. After a SearXNG update you may see a settings.yml.new next to your file. That's just SearXNG's newer template, left there for you to compare. Your own settings.yml stays the one in use.