summaryrefslogtreecommitdiff
path: root/utils/templates/etc/uwsgi/apps-archlinux
diff options
context:
space:
mode:
authorMarkus Heiser <markus.heiser@darmarIT.de>2025-07-11 16:53:36 +0200
committerGitHub <noreply@github.com>2025-07-11 16:53:36 +0200
commit574b285efa1658fd6d82d673e2063be659d5f624 (patch)
treea617a27c4e89ab1abfd30434490aba01c21f34ee /utils/templates/etc/uwsgi/apps-archlinux
parent9149175ff29afbba57fc899b1b555f70fa3b9d10 (diff)
[mod] remove option ui.static_use_hash (cache busting) (#5004)
Cache busting has caused serious problems for users in the past, here are two examples: - https://github.com/searxng/searxng/issues/4419 - https://github.com/searxng/searxng/issues/4481 And it makes development and deployment significantly more complex because it binds the client side to the server side: - https://github.com/searxng/searxng/pull/4466 In the light of a decoupled development of the WEB clients from the server side: - https://github.com/searxng/searxng/pull/4988 is it appropriate to abandon this feature. In fact, it has been ineffective since #4436 anyway. However, the benefit has always been questionable, since at best only a few kB of data are saved (at least in the context of an image_proxy, the effect is below the detection limit). Ultimately, the client is responsible for caching. Related: https://github.com/searxng/searxng/issues?q=label%3A%22clear%20browser%20cache%22 Closes: https://github.com/searxng/searxng/pull/4466 Closes: https://github.com/searxng/searxng/issues/1326 Closes: https://github.com/searxng/searxng/issues/964 Signed-off-by: Markus Heiser <markus.heiser@darmarit.de>
Diffstat (limited to 'utils/templates/etc/uwsgi/apps-archlinux')
-rw-r--r--utils/templates/etc/uwsgi/apps-archlinux/searxng.ini6
-rw-r--r--utils/templates/etc/uwsgi/apps-archlinux/searxng.ini:socket6
2 files changed, 2 insertions, 10 deletions
diff --git a/utils/templates/etc/uwsgi/apps-archlinux/searxng.ini b/utils/templates/etc/uwsgi/apps-archlinux/searxng.ini
index 12543cf5b..3388e432f 100644
--- a/utils/templates/etc/uwsgi/apps-archlinux/searxng.ini
+++ b/utils/templates/etc/uwsgi/apps-archlinux/searxng.ini
@@ -75,11 +75,7 @@ pythonpath = ${SEARXNG_SRC}
http = ${SEARXNG_INTERNAL_HTTP}
buffer-size = 8192
-# uWSGI serves the static files and in settings.yml we use::
-#
-# ui:
-# static_use_hash: true
-#
+# To serve the static files via the WSGI server
static-map = /static=${SEARXNG_STATIC}
static-gzip-all = True
offload-threads = %k
diff --git a/utils/templates/etc/uwsgi/apps-archlinux/searxng.ini:socket b/utils/templates/etc/uwsgi/apps-archlinux/searxng.ini:socket
index 0e6a7529d..4a55f0ab6 100644
--- a/utils/templates/etc/uwsgi/apps-archlinux/searxng.ini:socket
+++ b/utils/templates/etc/uwsgi/apps-archlinux/searxng.ini:socket
@@ -72,11 +72,7 @@ pythonpath = ${SEARXNG_SRC}
socket = ${SEARXNG_UWSGI_SOCKET}
buffer-size = 8192
-# uWSGI serves the static files and in settings.yml we use::
-#
-# ui:
-# static_use_hash: true
-#
+# To serve the static files via the WSGI server
static-map = /static=${SEARXNG_STATIC}
static-gzip-all = True
offload-threads = %k