About
This skill deploys a self-hosted SearXNG meta search engine using Docker Compose, covering configuration, engine selection, and Nginx setup. It's designed for developers who want to set up a private, untracked search engine that aggregates results from multiple providers. Use it when creating a shared search instance for teams or reducing reliance on single search providers.
Quick Install
Claude Code
Recommendednpx skills add pjt222/agent-almanac -a claude-code/plugin add https://github.com/pjt222/agent-almanacgit clone https://github.com/pjt222/agent-almanac.git ~/.claude/skills/deploy-searxngCopy and paste this command in Claude Code to install this skill
Documentation
Deploy SearXNG
Self-host SearXNG meta search → Docker Compose + Nginx.
Use When
- Private self-host search
- Aggregate multi-provider → no track
- Team/org shared instance
- Replace single provider
In
- Required: Server w/ Docker
- Optional: Domain
- Optional: SSL/Let's Encrypt
- Optional: Engine prefs
Do
Step 1: Scaffold
mkdir -p searxng/{config,nginx}
cd searxng
Step 2: Compose File
docker-compose.yml:
services:
searxng:
image: searxng/searxng:latest
container_name: searxng
volumes:
- ./config:/etc/searxng:rw
environment:
- SEARXNG_BASE_URL=https://search.example.com/
cap_drop:
- ALL
cap_add:
- CHOWN
- SETGID
- SETUID
restart: unless-stopped
networks:
- searxng
nginx:
image: nginx:1.27-alpine
container_name: searxng-nginx
ports:
- "8080:80"
volumes:
- ./nginx/nginx.conf:/etc/nginx/nginx.conf:ro
depends_on:
- searxng
restart: unless-stopped
networks:
- searxng
networks:
searxng:
driver: bridge
Step 3: Config SearXNG
config/settings.yml:
use_default_settings: true
general:
instance_name: "My SearXNG"
privacypolicy_url: false
contact_url: false
search:
safe_search: 0
autocomplete: "google"
default_lang: "en"
server:
secret_key: "generate-a-random-secret-key-here"
limiter: true
image_proxy: true
port: 8080
bind_address: "0.0.0.0"
ui:
static_use_hash: true
default_theme: simple
infinite_scroll: true
engines:
- name: google
engine: google
shortcut: g
disabled: false
- name: duckduckgo
engine: duckduckgo
shortcut: ddg
disabled: false
- name: wikipedia
engine: wikipedia
shortcut: wp
disabled: false
- name: github
engine: github
shortcut: gh
disabled: false
- name: stackoverflow
engine: stackoverflow
shortcut: so
disabled: false
- name: arxiv
engine: arxiv
shortcut: arx
disabled: false
Gen secret:
openssl rand -hex 32
Step 4: Nginx Front
nginx/nginx.conf:
events {
worker_connections 1024;
}
http {
server {
listen 80;
location / {
proxy_pass http://searxng:8080;
proxy_set_header Host $host;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header X-Forwarded-Proto $scheme;
proxy_set_header Connection "";
proxy_buffering off;
}
location /static/ {
proxy_pass http://searxng:8080/static/;
expires 1y;
add_header Cache-Control "public, immutable";
}
}
}
Step 5: Rate Limit
config/limiter.toml:
[botdetection.ip_limit]
link_token = true
[botdetection.ip_lists]
block_ip = []
pass_ip = ["127.0.0.1/8", "::1/128"]
pass_searxng_org = false
Step 6: Deploy + Verify
# Start stack
docker compose up -d
# Logs
docker compose logs -f searxng
# Check running
curl -s http://localhost:8080 | head -5
# Test search
curl -s "http://localhost:8080/search?q=test&format=json" | head -20
→ SearXNG on 8080 via Nginx. Queries → aggregated results.
If err: docker compose logs searxng → config err. Verify settings.yml YAML.
Step 7: SSL (Prod)
Public deploy → SSL termination. Update docker-compose.yml:
services:
nginx:
ports:
- "80:80"
- "443:443"
volumes:
- ./nginx/nginx-ssl.conf:/etc/nginx/nginx.conf:ro
- certbot-certs:/etc/letsencrypt:ro
- certbot-webroot:/var/www/certbot:ro
certbot:
image: certbot/certbot
volumes:
- certbot-certs:/etc/letsencrypt
- certbot-webroot:/var/www/certbot
volumes:
certbot-certs:
certbot-webroot:
See configure-nginx → full SSL Nginx config.
Step 8: Update + Maint
# Pull latest
docker compose pull searxng
# Restart w/ new img
docker compose up -d
# Backup config
cp -r config/ config-backup-$(date +%Y%m%d)/
Check
- SearXNG starts → no err logs
- Queries → results from configured engines
- Image proxy works
- Rate limiter blocks excess
- Config persists across restarts
- Nginx proxies correctly
Traps
- No secret_key: SearXNG refuses start w/o
secret_keyin settings.yml. - Config perms: SearXNG writes to config dir → volume
:rwnot:ro. - Engine blocks: Some engines block server IPs → rotate or image proxy.
- YAML indent:
settings.ymlindent-sensitive → lint before deploy. - Base URL mismatch:
SEARXNG_BASE_URLmust match actual URL, incl protocol + trailing slash. - Docker DNS: Google/Bing engines may need host net or proper DNS. Default Docker DNS OK.
→
setup-compose-stack— general Docker Compose patternsconfigure-nginx— Nginx SSL + security headersconfigure-reverse-proxy— advanced proxy patterns
GitHub Repository
Frequently asked questions
What is the deploy-searxng skill?
deploy-searxng is a Claude Skill by pjt222. Skills package instructions and resources that Claude loads on demand, so Claude can perform deploy-searxng-related tasks without extra prompting.
How do I install deploy-searxng?
Use the install commands on this page: add deploy-searxng to Claude Code as a plugin, or clone its repository into your skills directory, then restart Claude so it picks up the skill.
What category does deploy-searxng belong to?
deploy-searxng is in the Documentation category, tagged general.
Is deploy-searxng free to use?
Yes. deploy-searxng is listed on AIMCP and free to install. It runs inside Claude, so no separate service account is required to use the skill itself.
Related Skills
This skill fetches current Railway documentation to answer questions about features, functionality, or specific docs URLs. It ensures developers receive accurate, up-to-date information directly from Railway's official sources. Use it when users ask how Railway works or reference Railway documentation.
This Claude Skill provides expert guidance for writing Python code in n8n's Code nodes, specifically for using Python's standard library and working with n8n's special syntax like `_input`, `_json`, and `_node`. It helps developers understand Python's limitations within n8n and recommends using JavaScript for most workflows while offering Python solutions for specific data transformation needs.
The Archon skill provides RAG-powered semantic search and project management through a REST API. Use it for querying documentation, managing hierarchical projects/tasks, and performing knowledge retrieval with document upload capabilities. Always prioritize Archon first when searching external documentation before using other sources.
This Claude Skill provides expert guidance for writing JavaScript code in n8n's Code nodes. It covers essential n8n-specific syntax like `$input`/`$json` variables, HTTP helpers, and DateTime handling, while troubleshooting common errors. Use it when developing n8n workflows that require custom JavaScript processing in Code nodes.
