mirror of
https://github.com/searxng/searxng.git
synced 2025-08-11 14:26:43 +02:00
3de7a6da2d
Building the container currently does not work properly. When rebuilding several times with `make container`, `version_frozen.py` is recreated, which wouldn't be an issue if the file’s timestamp was constant. Now, when creating `version_frozen.py`, it will have the same timestamp as the commit when it was created. (`version_frozen.py` is moved to a dedicated layer). Reusing "builder" cache when building "dist" could be slow (CD reports 2 seconds, but locally I've seen it take up to 10 seconds), so the Dockerfile is now split and we save a couple steps by importing the "builder" image directly. The last changes made it possible to remove the layer cache in "builder", since the overhead is now greater than building the layers from scratch. Until now, all "dist" layers were squashed into a single layer, which in most cases is a good idea (except for storage/delivery pricing/overhead), but in our case, since we manage the entire pipeline, we can ignore this and share layers between builds. This means (for example) that if we change files unrelated to the container in several consecutive commits (documentation changes), we don't have to push the entire image to registry, but only the different layers (`version_frozen.py` in this example). The same applies when pulling, as only the layers that have changed compared to the local layers will be downloaded (that's the theory, we'll see if this works as expected or if we need to tweak something else). |
||
|---|---|---|
| .. | ||
| templates/etc | ||
| brand.sh | ||
| get_setting.py | ||
| lib.sh | ||
| lib_govm.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 | ||
| lib_valkey.sh | ||
| makefile.include | ||
| searxng.sh | ||
| searxng_check.py | ||