Can you add these new envs into the list: https://github.com/searxng/searxng/blob/master/Dockerfile#L18?

Thank you

Done.

Important note: this work with new installations, older installation keep the previous version of uwsgi.ini. But at least it fixes the issue for the preview-environments.

Added a commit on top that adds the same environment to the script installation procedure.

One question I have: should we also set offload-threads = %k from UWSGI_THREAD environment?

AFAIK the offload-threads setting is only for static files:

• https://uwsgi-docs.readthedocs.io/en/latest/StaticFiles.html#offloading
• https://uwsgi-docs.readthedocs.io/en/latest/OffloadSubsystem.html

The number of offload-threads never appeared to be an issue as far I know.
If we drop UWSGI in a near future, we won't have to explain this new env variable is not supported anymore.

I think these lines can be also removed

searxng/dockerfiles/docker-entrypoint.sh

Lines 62 to 70 in 76b91a3

	patch_uwsgi_settings() {
	CONF="$1"
	# update uwsg.ini
	sed -i \
	-e "s|workers = .*|workers = ${UWSGI_WORKERS:-%k}|g" \
	-e "s|threads = .*|threads = ${UWSGI_THREADS:-4}|g" \
	"${CONF}"
	}

I have seen these lines in my review, but I think we can't ...

The template is copied with out a replacement from the environment:

Now we have a uwsg.ini with the raw strings $(UWSGI_WORKERS) & $(UWSGI_THREADS) in ..

After the copy this raw strings will be patched by patch_uwsgi_settings() function ..

@dalf: after rethinking about theses lines; its no longer clear to me if it was intended.

When should $(UWSGI_WORKERS) & $(UWSGI_THREADS) be set .. from the environment when the uwsgi service is started? .. or from the patch_uwsgi_settings() when the service is installed?

.. can you have a look / thanks!

I think these lines can be also removed

(reposting with the correct account)