* [fix] container: remove static hashing
Allows browser cache heuristics to properly work.
Related https://github.com/searxng/searxng/pull/5006
Closes https://github.com/searxng/searxng-docker/issues/409
* [fix] container: don't revalidate at every request
As Granian no longer handles static files directly, the whole process goes through Flask, which apart from being slow, is resource intensive, even to serve HTTP 304 responses.
* rework Caddyfile
* fix missing "public" directive
* features cleanup
Since this header is attached to each outgoing request the overall size is slightly increased by 300 bytes, we don't care if the site is allowed to play media in the background, so with the vast majority of features that have been added (and those that were already present)
* restore encode directive
Caddyserver actually did passthrough the precompressed resources served by uWSGI (Oops)
* merge upstream changes
* fix typo
---------
Co-authored-by: Émilien (perso) <4016501+unixfox@users.noreply.github.com>
* Update: grammatical correctness in README.md
* Update: grammatical accuracy on README.md
* Update: enhance readability and include proper syntax highlighting for the commands under "Start SearXNG with systemd" in README.md
Update: enhance readability and include proper syntax highlighting for the commands under "Start SearXNG with systemd" in README.md
Update README.md
Update README.md
Update README.md
Update: enhance readability and included proper syntax highlighting for the commands under "Start SearXNG with systemd" in README.md
Update: Space Fix!
Update: Space Fixing in cp command
Add instructions to the `README.md` for removing `cap_drop: - ALL` on the first run.
* **Explanation**: Add a note explaining that `cap_drop: - ALL` must be removed from the `docker-compose.yaml` file for the `searxng` service to successfully create `/etc/searxng/uwsgi.ini`.
* **Reason**: Explain that the `cap_drop: - ALL` directive removes all capabilities, including those required for the creation of the `uwsgi.ini` file.
---
For more details, open the [Copilot Workspace session](https://copilot-workspace.githubnext.com/IAmStoxe/searxng-docker?shareId=XXXX-XXXX-XXXX-XXXX).
* replace with official image
* use `7-alpine` tag
* prevent collision with other volumes
* Revert editing README formatting
---------
Co-authored-by: Émilien (perso) <4016501+unixfox@users.noreply.github.com>
* Update README to use newer docker compose command
* Update README to add note about docker < 3.6.0 and docker-compose
* Update the docker compose install url
- edit the content of ```WorkingDirectory``` in the ```searxng-docker.service``` file (only if the installation path is different from /usr/local/searxng-docker)
- Install the systemd unit:
```sh
systemctl enable $(pwd)/searxng-docker.service
systemctl start searxng-docker.service
```
## Note on the image proxy feature
The SearXNG image proxy is activated by default.
The default [Content-Security-Policy](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Content-Security-Policy) allow the browser to access to ```${SEARXNG_HOSTNAME}``` and ```https://*.tile.openstreetmap.org;```.
If some users wants to disable the image proxy, you have to modify [./Caddyfile](https://github.com/searxng/searxng-docker/blob/master/Caddyfile). Replace the ```img-src 'self' data: https://*.tile.openstreetmap.org;``` by ```img-src * data:;```.
## Multi Architecture Docker images
Supported architecture:
- amd64
- arm64
- arm/v7
## How to update ?
To update the SearXNG stack:
```sh
docker-compose pull
docker-compose down
docker-compose up
```
To update this `docker-compose.yml` file:
Check out the newest version on github: [searxng/searxng-docker](https://github.com/searxng/searxng-docker).
Continue to [*searxng-docker*](https://github.com/searxng/searxng-docker/tree/0c7875a42942e916ab39b171d69cab7d170ddb60) (deprecated)
# see https://docs.searxng.org/admin/engines/settings.html#use-default-settings
use_default_settings:true
server:
# base_url is defined in the SEARXNG_BASE_URL environment variable, see .env and docker-compose.yml
secret_key:"ultrasecretkey"# change this!
limiter:true# can be disabled for a private instance
image_proxy:true
ui:
static_use_hash:true
redis:
url:redis://redis:6379/0
Reference in New Issue
Block a user
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.