Coolify Ops

Remotely operate a Coolify instance through the official coolify CLI (the Go version, coollabsio/coolify-cli). This skill assumes the target is the user's own self-hosted Coolify (typically: one VPS + a handful of deployed Node/Next.js/Docker services).

Core Principles

1. For everything in this skill's scope, the CLI is an HTTP API client — not SSH. All the operations covered here (deploy / app / service / database / env / logs / backup — the entire v1.6.2 command surface) go through the Coolify REST API with a Bearer token; they have nothing to do with the server's SSH credentials. If a command can't connect, suspect API reachability and the token first, not SSH.

   [ALPHA] — experimental Coolify v5 commands, out of scope here. The Coolify v5 roadmap adds SSH-based bootstrap commands that, unlike everything above, run over SSH + root:

   • init — provisions a host (WireGuard mesh + Podman) over SSH.
   • firewall — manages a COOLIFY-ALLOW iptables chain / cross-host container rules over SSH.
   • common sshmesh — the underlying SSH-mesh plumbing.

   ⚠️ These are not present in the verified v1.6.2 binary (coolify --help does not list them), so this skill neither uses nor documents them as usable — treat any such command as experimental, root-level, and not a stable feature; verify against your own CLI build before touching it. In particular, do not confuse a future firewall command (which manages mesh container rules) with hardening a public database port — restricting a public DB port's source IPs is still done with ufw / your cloud security group, which is a different thing entirely (see references/database-access.md §2.3).