What problem does it solve? Deploying a Go Gin API to production involves many error-prone decisions: choosing base images, writing multi-stage Dockerfiles, wiring docker-compose services with health checks, and adding observability. This Skill provides production-tested patterns for each step so you avoid common pitfalls like bloated images, leaked secrets, and hanging health probes. ## Core Features & Use Cases - Multi-Stage Docker Builds: Build ~10 MB distroless images with CGO_ENABLED=0, ldflags stripping, BuildKit cache mounts, and non-root execution. - Docker Compose Environments: Set up development stacks with Air hot reload, integration test compose files, and production-like compose with resource limits and health checks. - Health Checks & 12-Factor Config: Implement /health endpoints with DB ping timeouts, readiness vs liveness probes, and environment-variable-based configuration with fail-fast validation. - OpenTelemetry Observability: Add tracing, RED metrics, log-trace correlation, and Jaeger/Prometheus/Grafana compose stacks with graceful shutdown. - Use Case: You have a Gin API running locally and need to ship it. Use this Skill to generate a hardened production Dockerfile, a docker-compose stack with Postgres and Redis health checks, and OTel instrumentation before your first deploy. ## Quick Start Dockerize my Go Gin API with a multi-stage Dockerfile and a docker-compose setup including Postgres, Redis, and health checks.
