sc-dokploy

# /sc-dokploy — Dokploy CRUD & Audit Use this skill when the user wants to inspect, change, or clean up Dokploy state directly (without redeploying code). ## Pre-requisites - `DOKPLOY_API_URL`, `DOKPLOY_API_KEY` — Dokploy admin - SSH fallback to the Dokploy host (for orphan swarm services / Traefik file CRUD the REST API does NOT expose): `ssh -i ~/.ssh/<your_key> <user>@<your-dokploy-host>` with passwordless sudo. If missing, route to `/sc-onboarding`. ## Connection-safe local execution When Dokploy access is stored in an SI-Coder named `source=sc` connection, run credential-dependent commands through `sc run -- ...` so the selected connection is injected only into that child process: ```bash sc run -- node skills/sc-dokploy/scripts/projects.js list ``` The shorter `node scripts/...` examples below describe the script interface and are valid only when the required environment is already supplied by the caller. Do not export Dokploy credentials globally just to use them. External/provider-managed sources must execute through their own connection backend instead of `sc run`. ## REST vs SSH Dokploy REST API covers projects, applications, compose, domains, deploy/start/stop, monitoring read. It does **NOT** cover: - `docker service rm` (orphan swarm services) - `rm /etc/dokploy/traefik/dynamic/<file>.yml` (orphan Traefik routers) - container exec / kill / log tail beyond the dashboard For those, SSH in directly. Useful one-liners: ```bash ssh -i ~/.ssh/<your_key> <use...