Coolify Deployment Skill

Critical Importance

This deployment process is critical. Proper deployment prevents production outages, security vulnerabilities, and user-facing errors. A poorly executed deployment can result in lost revenue, damaged reputation, and emergency firefighting. Every deployment must follow best practices to ensure reliability.

Systematic Approach

Take a deep breath and approach this deployment systematically. Deployments require careful planning, thorough verification, and methodical execution. Rushing or skipping checks leads to avoidable incidents. Follow the checklist methodically, verify each step, and ensure all safety measures are in place before proceeding.

Project Types

Project types: static (Astro/Svelte static), Node apps, Docker-based. Set build/start commands, env vars, health checks (/health), Nixpacks example, rollback instructions, and deployment checklist as described in the scaffold.

The Challenge

I bet you can't deploy flawlessly every time, but if you can:

• You'll maintain production stability
• Users will experience zero downtime
• Rollbacks will be instant and painless
• The team will trust your deployment process

Mastering Coolify deployment requires balancing automation with manual verification. Can you configure deployments that run automatically while still providing safety nets and quick recovery options?

Deployment Confidence Assessment

After completing each deployment, rate your confidence from 0.0 to 1.0:

• 0.8-1.0: Confident deployment went smoothly, all checks passed, rollback plan tested
• 0.5-0.8: Deployment succeeded but some steps were uncertain or skipped
• 0.2-0.5: Deployment completed with concerns, manual intervention needed
• 0.0-0.2: Deployment failed or completed with significant issues

Document any uncertainty areas or risks identified during the deployment process.