validate-coolify-compose

To validate a docker-compose file for Coolify, you provide the YAML configuration and the tool evaluates port exposure, fixed image tags, restart policies, healthchecks, and volume persistence. It analyzes the file line by line to detect deployment-breaking configurations and outputs a structured compliance report.

Deployments on VPS, Cloudflare, and Traefik break when web services expose ports directly, use network_mode: host, or rely on floating image tags like latest. Additional rule violations include missing healthchecks, hardcoded credentials in env variables, and absent restart: unless-stopped policies.

Yes, Coolify requires using expose instead of ports for web services to prevent direct port exposure. This rule enforces secure traffic routing through reverse proxies like Traefik rather than allowing direct external access to the underlying containers.

Using fixed image versions instead of latest for Docker production prevents unexpected breaking changes from upstream updates. This validation process enforces strict version tagging to ensure stable and predictable application deployments across your Coolify infrastructure.

To check if volumes and dependencies are configured correctly, validation rules verify that critical data uses persistent volumes and service dependencies are explicitly defined. This ensures data survives container restarts and startup order is maintained for production stability.