mirror of
https://github.com/searxng/searxng.git
synced 2025-07-13 00:09:18 +02:00
eb36de8d91
Some checks failed
Documentation / Release (push) Has been cancelled
Integration / Python 3.10 (push) Has been cancelled
Integration / Python 3.11 (push) Has been cancelled
Integration / Python 3.12 (push) Has been cancelled
Integration / Python 3.13 (push) Has been cancelled
Integration / Python 3.9 (push) Has been cancelled
Integration / Theme (push) Has been cancelled
I'm not too pleased to reverse this, but issues like https://github.com/searxng/searxng/issues/4792 have not been foreseen, and we can't just turn away. It has become apparent over the last weeks that there are still quite a few people with an incompatible CPU or having SearXNG on some random VM provider who can't (or won't) modify the configuration of their machines to expose the features needed for x86_64v2 march. As I don't want to trash the work with apko and base images, I thought about trying building Alpine again now that we have all the container related workflow refactored. There will still be the discussion of whether to use musl and its drawbacks, but right now I don't know any other alternatives. The nice part of this is that both Dockerfiles (mainline and legacy) can now be unified under the same umbrella again. Closes https://github.com/searxng/searxng/issues/4792 Closes https://github.com/searxng/searxng/issues/4753 |
||
|---|---|---|
| .. | ||
| templates | ||
| brand.sh | ||
| get_setting.py | ||
| lib.sh | ||
| lib_go.sh | ||
| lib_nvm.sh | ||
| lib_redis.sh | ||
| lib_sxng_container.sh | ||
| lib_sxng_data.sh | ||
| lib_sxng_node.sh | ||
| lib_sxng_static.sh | ||
| lib_sxng_test.sh | ||
| lib_sxng_themes.sh | ||
| lib_sxng_vite.sh | ||
| lib_sxng_weblate.sh | ||
| lxc-searxng.env | ||
| lxc.sh | ||
| makefile.include | ||
| makefile.lxc | ||
| searxng.sh | ||
| searxng_check.py | ||