Added default SearXNG configuration files (settings.yml and limiter.toml) to the service startup command, enabling proper setup with user-agent, bind address, and rate limiting. Introduced a new required PIPELINES_API_KEY environment variable with auto-generation using openssl, ensuring pipeline authentication is configured out of the box.
- Introduce `PIPELINES_API_KEY` in the secrets file to secure pipelines communication
- Replace hardcoded RAG and web search URLs with template variables, enabling flexible configuration
- Add new template variables (`ENABLE_WEB_SEARCH`, `WEB_SEARCH_ENGINE`, `WEB_LOADER_ENGINE`, `SEARXNG_QUERY_URL`, `EXTERNAL_WEB_LOADER_URL`) with defaults
- Include OpenWebUI secret env file in the service definition for consistent secret injection
- Set `ENABLE_PERSISTENT_CONFIG` to false to align with the parametrized deployment approach
These changes decouple service endpoints from the deployment template, allowing users to easily customize web search and RAG integrations without modifying service definitions.
Add a new required secret key `SECRET_KEY` referencing `CRAWL4AI_SECRET` in the openwebui-secret configuration, and define the corresponding template entry with generation via `openssl hex 32`. This enables secure authentication for the Crawl4AI integration.
Added new searxng and crawl4ai services with their secrets and environment variables for web search and crawling. Updated existing container names to use `-app` suffix and adjusted references. Added necessary directory creation for new services.
