docker-selfhost

What problem does it solve?

This Skill solves the problem of setting up and operating reliable self-hosted Docker services—especially when containers restart, data isn’t persisting, HTTPS/proxying is misconfigured, containers can’t reach each other, or a stack must be migrated and backed up.

Core Features & Use Cases

• Compose-first, production-ready setups: Generates pinned Docker Compose stacks with sensible defaults for reproducibility and maintainability.
• Persistence that survives real life: Chooses bind mounts (and ZFS-friendly paths on TrueNAS SCALE) for snapshotable, migratable data.
• Reverse proxy and secure exposure: Recommends Traefik with TLS, LAN-only Nginx Proxy Manager, or zero-trust Cloudflare Tunnel depending on access needs.
• Container networking patterns: Uses named networks for service-to-service communication and host networking only when required by device protocols.
• Operational safeguards: Avoids common anti-patterns like latest tags, leaking secrets, exposing DB ports publicly, or skipping healthy start ordering and tested backups.

Quick Start

Use the docker-selfhost skill to design a Docker Compose stack that runs a self-hosted service behind Traefik with HTTPS, persists its data on a ZFS dataset (or bind mount), and connects it to other containers via a named network.