Deploy SearXNG privacy-focused metasearch engine as infrastructure service for core-ai web search capabilities. Changes: - Add SearXNG Docker Compose stack - Image: searxng/searxng:latest - Port: 8087 (HTTP API with JSON format) - Network: docker-dataplane (shared with core-ai) - Storage: Config only at ~/docker-data/searxng - Redis integration: DB 5 on redis-shared for result caching - Resource limits: 1 CPU, 512MB RAM - Health check: /healthz endpoint Features: - Aggregates 246+ search engines (Google, Bing, DuckDuckGo, etc.) - Privacy-first: No tracking, no profiling, no data collection - Multi-format: HTML (web UI), JSON (API for core-ai) - Configurable categories: general, it, science, news, images, videos, etc. - Result caching via Redis (reduces duplicate queries) Search Categories: - general: Web search - it: Programming/technical (StackOverflow, GitHub, documentation) - science: Academic (arXiv, PubMed, Semantic Scholar) - news: News articles - images/videos: Media search - map: Geographic/location queries Integration: - Core-AI web_search tool uses http://searxng:8080/search API - JSON format enabled for programmatic access - Timezone: Europe/Amsterdam Security: - Dropped all capabilities except essential (CHOWN, SETGID, SETUID) - No data persistence (privacy by design) - Internal network only (not exposed via NPM) Setup: 1. mkdir -p ~/docker-data/searxng 2. docker-compose -f stacks/searxng.yml up -d 3. Verify: curl "http://localhost:8087/search?q=test&format=json" API Usage: GET http://searxng:8080/search?q=query&format=json&categories=general Resource Usage: - CPU: ~0.2-0.5 cores - RAM: ~150-300MB - Disk: ~10-50MB (config only) 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>
portainer-core
Self-hosted home server infrastructure with GPU-accelerated ML, AI orchestration, media streaming, and secure remote access
Main Dashboard: https://home.schweitz.net (Organizr)
Quick Links
Getting Started
- System Specifications - Hardware and software details
- Container Reference - All deployed services
- Current Status - Implementation progress and phase tracking
Implementation Plans
- Implementation Plans - Master plan tracker
- Active Plans - Current development work
- Completed Plans - Historical implementations
Documentation Index
Architecture & Design
- Shared Infrastructure Architecture - PostgreSQL/Redis shared infrastructure
Operational Guides
- Backup Procedures - Backup strategies and procedures
- Code-Server Setup - Browser-based IDE configuration
- Connect Devices Guide - Headscale VPN setup
- GPU Docker Configuration - NVIDIA GPU passthrough
- Headscale Setup - Mesh VPN deployment
- NPM Logging Guide - Nginx Proxy Manager logging
Services
- Core API - Infrastructure management and AI orchestration
- Organizr Widgets - Service control dashboard
Reference
- Stacks Reference - All Docker Compose stacks
- Scripts Reference - Maintenance automation
- Automation Reference - Portainer REST API usage
- Container Reference - Complete container profiles
- System Reference - Hardware specifications
- Changelog - Version history
For AI Agents
- Agent Guidelines - REQUIRED READING for all LLM coding agents
Architecture Overview
┌─────────────────────────────────────────┐
│ Infrastructure Layer │
│ ├── Portainer (8080) - Container mgmt │
│ ├── PostgreSQL Shared (5432) - DB │
│ ├── Redis Shared (6379) - Cache │
│ ├── NPM (8000) - Reverse proxy │
│ └── Ollama (11434) - ML models [GPU] │
├─────────────────────────────────────────┤
│ Networking Layer │
│ ├── docker-dataplane - Service mesh │
│ └── Headscale (8085) - VPN mesh │
├─────────────────────────────────────────┤
│ Monitoring Layer │
│ ├── Uptime Kuma (3001) - Uptime │
│ ├── Netdata (19999) - Metrics │
│ └── Organizr (8084) - Dashboard │
├─────────────────────────────────────────┤
│ Optimization Layer │
│ ├── Watchtower - Auto-updates │
│ └── Maintenance - Automated backups │
├─────────────────────────────────────────┤
│ Application Layer │
│ ├── Open WebUI (8081) - LLM chat UI │
│ ├── Core API (8083) - Infra mgmt │
│ ├── Jellyfin (8096) - Media [GPU] │
│ ├── Nextcloud (8082) - Cloud storage │
│ ├── Gitea (3002) - Git hosting │
│ └── Samba (445) - File shares │
└─────────────────────────────────────────┘
Project Structure
portainer-core/
├── plans/ # Implementation plans
│ ├── active/ # Current development work
│ └── completed/ # Historical implementations
├── docs/ # Documentation
│ ├── architecture/ # Design documents
│ ├── guides/ # Setup and operational guides
│ ├── services/ # Service-specific documentation
│ └── reference/ # Quick reference materials
├── stacks/ # Docker Compose files (version-controlled)
├── scripts/ # Maintenance automation
├── services/ # Service source code
│ ├── core-api/ # Infrastructure management API
│ └── ...
├── organizr-widgets/ # Dashboard widgets
├── AGENTS.md # AI agent guidelines (single source of truth)
├── README.md # This file (documentation index)
├── PLANS.md # Implementation plan tracker
├── STATUS.md # Current phase tracking
└── CHANGELOG.md # Version history
Common Commands
Infrastructure Management
make status # Show running containers and system status
make health # Comprehensive health check
make gpu-check # Verify GPU passthrough
make disk # Disk usage report
make backup # Backup Docker configs
make cleanup # Clean unused Docker resources
Stack Management
make deploy-portainer # Deploy Portainer
make deploy-ollama # Deploy Ollama
make logs-ollama # View Ollama logs
make update-jellyfin # Update Jellyfin to latest
make stop-nextcloud # Stop Nextcloud stack
See Stacks Reference for complete stack inventory and deployment procedures.
Development Setup
Python Environment
Some automation scripts require Python dependencies:
# Activate virtual environment
source .venv/bin/activate
# Install/update dependencies
pip install -r requirements.txt
# Deactivate when done
deactivate
Service Development
See individual service documentation:
Service Ports Reference
| Service | Port | Description |
|---|---|---|
| Portainer | 8080 | Container management UI |
| Nginx Proxy Manager | 8000 | Reverse proxy admin |
| Open WebUI | 8081 | LLM chat interface |
| Nextcloud | 8082 | Cloud storage |
| Core API | 8083 | Infrastructure management API |
| Organizr | 8084 | Unified dashboard |
| Headscale | 8085 | VPN control server |
| Jellyfin | 8096 | Media streaming |
| Uptime Kuma | 3001 | Service monitoring |
| Gitea | 3002 | Git repository hosting |
| Gitea SSH | 2222 | Git SSH access |
| PostgreSQL Shared | 5432 | Shared database (internal) |
| Redis Shared | 6379 | Shared cache (internal) |
| Qdrant | 6333, 6334 | Vector database |
| Ollama | 11434 | ML model API |
| Netdata | 19999 | System monitoring |
See Stacks Reference for complete port allocation.
GPU Services
Two services leverage the RTX 2080 Ti:
- Ollama - ML model inference (3B-13B parameter models)
- Jellyfin - Hardware video transcoding (NVENC)
See GPU Docker Configuration for setup.
Storage Strategy
SSD (Performance): /home/jpmschweitzer/docker-data/
- Docker configs, databases, cache, container images
HDD (Capacity): /mnt/media/
- Media files, user data, backups
See Stacks Reference for details.
Current Phase
Phase 2 of AI Orchestrator Enhancement (Memory Systems) 🔄 In Progress
See STATUS.md for detailed progress tracking.
Contributing
This is a personal infrastructure project. For AI agents:
- Read AGENTS.md first - Mandatory guidelines
- Follow conventional commit format
- Test GPU access before deploying GPU services
- Update STATUS.md when completing phases
Resources
Version: 0.7.1 Last Updated: 2025-11-20 System: tower-of-joy