coolify-clilisted

# Coolify CLI The `coolify` CLI manages Coolify instances (Coolify Cloud and self-hosted). It wraps the Coolify REST API (`/api/v1/`) and covers servers, projects, applications, databases, one-click services, deployments, environment variables, backups, private keys, and GitHub App integrations. Everything you need is reachable through `coolify <noun> <verb>`. This file covers the mental model, auth, and the most common workflows. Detailed command-by-command reference lives in `references/` — read the relevant file when you need exact flags. ## Mental model Coolify's object hierarchy, from outside in: ``` context (an instance: cloud or self-hosted URL + token) └─ server (a machine Coolify deploys onto) └─ project └─ environment (e.g. "production") └─ resource ─┬─ application (git repo, Dockerfile, or image) ├─ database (postgres, mysql, redis, ...) └─ service (one-click stacks) ``` Key facts that save round-trips: - **Almost everything is addressed by UUID, not name.** Run a `list` first to find the UUID, then act on it. The *one* exception is teams, which use numeric IDs. - **You usually need both a `--project-uuid` and a `--server-uuid` to create a resource.** Get them from `coolify project list` and `coolify server list`. - **Sensitive fields (tokens, passwords, IPs, emails) are hidden by default.** Add `-s` / `--show-sensitive` to reveal them. - **Output i