Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
services:searxng [2024/07/30 11:35] – willy | services:searxng [2024/11/11 06:54] (current) – external edit 127.0.0.1 | ||
---|---|---|---|
Line 5: | Line 5: | ||
===== Installation ===== | ===== Installation ===== | ||
- | There are multiple installation approaches possible. You can either go with containers or bare-metal. While i usually | + | There are multiple installation approaches possible. You can either go with containers or bare-metal. While i usually |
- | So, as usual create the user and clone the repo and copy the compose yaml | + | So, as usual create the user, then clone the repository |
<code bash> | <code bash> | ||
- | useradd -d /deposito/ | + | useradd -d /data/ |
su - searxng | su - searxng | ||
git clone https:// | git clone https:// | ||
Line 15: | Line 15: | ||
</ | </ | ||
- | Now you don't want Caddy because you already have NGINX as reverse proxy, so : | + | Now you don't want Caddy because you already have NGINX as reverse proxy, so edit the docker compose file like the following example: |
<file - docker-compose.yml> | <file - docker-compose.yml> | ||
version: " | version: " | ||
Line 43: | Line 43: | ||
networks: | networks: | ||
- | | + | |
ipam: | ipam: | ||
driver: default | driver: default | ||
Line 55: | Line 55: | ||
Remember to set an available port (8083)! | Remember to set an available port (8083)! | ||
- | Now pull and start it: | + | Now pull it: |
<code bash> | <code bash> | ||
podman compose pull | podman compose pull | ||
</ | </ | ||
- | To start it, and set it up on boot, as usual check [[gentoo: | ||
- | <code bash | ||
- | cd / | ||
- | ln -s _servicer.sh 21-searxng--podman.start | ||
- | ln -s _servicer.sh 21-searxng--podman.stop | ||
- | </ | ||
- | |||
- | You can start it now by running the above start link. | ||
===== Reverse Proxy ===== | ===== Reverse Proxy ===== | ||
- | Following [[https:// | + | You can run SearXNG both as a subdomain or a subpath. I prefer the first one because it make it easier to integrate as Firefox default search engine. |
- | <file - searxng.conf> | + | |
- | location /searxng/ { | + | |
- | proxy_pass http://127.0.0.1:8083/; | + | I assume the SearXNG will be reachable as **https://search.mydomain.com**. |
- | proxy_set_header | + | Following [[https:// |
- | | + | <file - search.conf> |
+ | server { | ||
+ | server_name search.mydomain.com; | ||
+ | listen 443 ssl; | ||
+ | listen 8443 ssl; | ||
+ | http2 on; | ||
- | # see flaskfix.py | + | |
- | proxy_set_header | + | |
- | | + | |
- | # see limiter.py | + | location / { |
- | proxy_set_header | + | |
- | proxy_set_header | + | |
- | # proxy_buffering | + | proxy_pass http:// |
- | # proxy_request_buffering off; | + | |
- | # proxy_buffer_size 8k; | + | |
- | access_log /dev/null; | + | proxy_set_header |
- | | + | |
+ | # see flaskfix.py | ||
+ | proxy_set_header | ||
+ | proxy_set_header | ||
+ | |||
+ | # see limiter.py | ||
+ | proxy_set_header | ||
+ | proxy_set_header | ||
+ | |||
+ | access_log /dev/null; | ||
+ | error_log | ||
+ | } | ||
} | } | ||
</ | </ | ||
Line 100: | Line 101: | ||
and add it to your NGINX configuration. See [[selfhost: | and add it to your NGINX configuration. See [[selfhost: | ||
+ | SSO can be added using the **basic** endpoint in Authelia or NGINX PAM Auth. | ||
+ | |||
+ | ===== Add to firefox ===== | ||
+ | |||
+ | Navigate your firefox to **https:// | ||
===== Autostart ===== | ===== Autostart ===== |