coolify-deploy-checklist

Validating docker-compose before Coolify deployment involves checking for critical prohibitions like host network mode, plaintext credentials, and latest image tags, while ensuring healthchecks and restart policies are defined.

Security checks for docker-compose before CI/CD deployment include avoiding mapped ports on web services, preventing plaintext credentials, and prohibiting network_mode: host and latest image tags to ensure safe production pushes.

Coolify deployments may fail validation when critical services lack defined healthchecks, explicit exposes, persistent volumes, or proper restart policies, as these mandatory deployment rules must be satisfied before pushing to production.

No, you cannot use network_mode: host when deploying docker-compose to Coolify, as the validation process enforces a critical prohibition against host network mode to ensure secure and isolated production deployments.

Mandatory docker-compose requirements for Coolify include defining healthchecks for critical services, configuring persistent volumes, documenting internal ports, and setting explicit restart policies to pass validation.