setup-coolifylisted
Install: claude install-skill Streamlinity/claude-skills-deploy
# setup-coolify
Arguments: `$ARGUMENTS`
Provision or update a Coolify + Doppler deployment from `coolify.yaml` in the current
working directory. Same skill works for any repo and any Coolify server — the `server:`
alias in `coolify.yaml` selects both the Coolify URL and the Doppler account.
## Subcommands
| Form | Action |
|------|--------|
| `/setup-coolify` | Provision/update: ensures Doppler keys exist, upserts every app in the `environments:` map (staging + production required; extra envs like `qa` provisioned identically), syncs env vars, mounts Doppler-fallback volume. Does NOT deploy — the first deploy fires on push to `main` via the generated workflow. Idempotent. |
| `/setup-coolify provision` | Explicit alias for blank — same as `/setup-coolify` with no arguments. Provision/update all apps idempotently. |
| `/setup-coolify plan` | Read-only diff (Terraform-style): runs `provision.sh --plan`, reporting `+ CREATE` / `= EXISTS` / `~ PATCH` per resource (project, apps, volumes, Doppler tokens, DNS records) against live state, then exits. Nothing is mutated. Use before re-running provision on a production server. |
| `/setup-coolify seed` | Explicit Doppler gap-fill from `.env.local` (seeds `dev` + `stg`) and `.env.production` (seeds `prd`). Runs `bash $HOME/.claude/skills/setup-coolify/scripts/seed.sh`. Logs every key set. Never overwrites an existing Doppler value. Run after creating a new repo's Doppler project before running provision. |
| `/setup-coolify init_ci