coolify-deploy

Automate governed Coolify deployments on DigitalOcean droplets with staging and approval gates.

Updated Apr 18, 2026
One-click install
npx skills add https://github.com/Flintmere/flintmere --skill coolify-deploy-flintmere
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: coolify-deploy
Source: https://github.com/Flintmere/flintmere/tree/main/.claude/skills/coolify-deploy
Command: npx skills add https://github.com/Flintmere/flintmere --skill coolify-deploy-flintmere

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates safe, governed Coolify deployment practices on Flintmere's DigitalOcean droplet, ensuring configuration integrity and auditable operations.

Core Features & Use Cases

  • Staged deployment workflow with a mandatory first-deploy gate to prevent production pushes without operator review.
  • Automated generation and validation of Dockerfile, docker-compose, Traefik routing, SSL setup, and provisioning of Postgres/Redis, plus centralized secrets management.
  • Runbook generation and policy-driven safeguards for upgrades, secret rotation, and daily backups to DigitalOcean Spaces.

Quick Start

Review the deployment brief and perform a staging Coolify deploy according to the first-deploy gate and backup policies.

Frequently Asked Questions about coolify-deploy

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate Coolify deployments on a DigitalOcean droplet?

Automate Coolify deployments on a DigitalOcean droplet using a policy-driven workflow that provisions Postgres and Redis, configures Traefik routing, and enforces staging gates before production. It generates Dockerfiles, docker-compose files, and Let's Encrypt SSL setups to ensure configuration integrity.

What is the best way to manage secrets and environment variables in Coolify?

Manage secrets and environment variables in Coolify through a centralized, policy-driven governance model that supports secure secret rotations. The workflow enforces operator approval for production deployments and maintains auditable operations alongside automated nightly backups to DigitalOcean Spaces.

Can I deploy directly to production with Coolify without operator approval?

Direct production deploys without operator approval are disallowed by the first-deploy gate. The workflow mandates a staged deployment process, requiring successful staging validation and explicit operator review before any application or service is pushed to the production environment.

How do I configure Traefik routing and Let's Encrypt SSL for Coolify services?

Configure Traefik routing and Let's Encrypt SSL for Coolify services through automated generation and validation of routing configurations. The workflow handles Dockerfile and docker-compose provisioning, automatically applying SSL certificates and routing rules for new services deployed on the droplet.

Does this Coolify deployment workflow support droplet upgrades and nightly backups?

This Coolify deployment workflow fully supports droplet upgrades and nightly backups through built-in runbook generation and policy-driven safeguards. It performs automated daily backups to DigitalOcean Spaces and provides structured guidance for safely upgrading droplets and rotating secrets.

Why does my Coolify deployment require a staging environment first?

Your Coolify deployment requires a staging environment first to prevent unreviewed production pushes and ensure configuration integrity. The mandatory first-deploy gate acts as a safeguard, validating Dockerfile, Traefik, and database configurations before allowing any production release.