dokploy-cli

Manage Dokploy services, deployments, domains, and databases via the official @dokploy/cli.

Updated Feb 6, 2026
One-click install
npx skills add https://github.com/maycuatroi1/agent-skills --skill dokploy-cli-maycuatroi1
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dokploy-cli
Source: https://github.com/maycuatroi1/agent-skills/tree/main/skills/dokploy-cli
Command: npx skills add https://github.com/maycuatroi1/agent-skills --skill dokploy-cli-maycuatroi1

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires @dokploy/cli, and includes scripts (resource) components.

What problem does it solve? Managing Dokploy panels through the web UI is slow and hard to script, and hand-rolled curl calls against the API are fragile. This Skill wraps the official @dokploy/cli (449 commands across 32 groups) so you can list services, deploy apps, update env vars, and manage databases from the terminal with JSON output. ## Core Features & Use Cases - One-shot idempotent installer: scripts/install.sh handles npm install, credential verification against ~/.omelet.json, shell rc wiring, and a smoke test in a single re-runnable step. - Full service management: projects, applications, compose services, postgres/mysql/mariadb/mongo/redis databases, domains, certificates, backups, schedules, and rollbacks, all with --json output for jq piping. - Credential lifecycle integration: env vars are sourced from ~/.omelet.json via export_dokploy_env.sh, surviving npm upgrades and roaming across machines through the credentials-utils sync workflow. - Use Case: You need to update one env var on a compose service and redeploy. The Skill provides the read-mutate-write pattern (no atomic set-key command exists) plus a deploy-status polling loop. ## Quick Start Ask the agent to set up the Dokploy CLI on this machine and list all projects and their services.

Frequently Asked Questions about dokploy-cli

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

FAQPage Schema
How do I install and set up the Dokploy CLI on a new machine?

Run bash skills/dokploy-cli/scripts/install.sh for a one-shot idempotent setup. It installs @dokploy/cli via npm, verifies dokploy_url and dokploy_api_key in ~/.omelet.json, appends the env export line to your shell rc, and runs a smoke test with dokploy project all.

How do I update a single environment variable on a Dokploy compose service?

There is no atomic set-one-key command; the API takes the entire env blob. Read the current env with dokploy compose one --json, mutate the multi-line string with awk or similar, then write it back with dokploy compose update --composeId <id> --env.

Where does the Dokploy CLI store its API token?

This Skill avoids dokploy auth, which writes the token inside the npm package and loses it on reinstall. Instead it exports DOKPLOY_URL and DOKPLOY_API_KEY from ~/.omelet.json via a sourced shell script, so auth survives upgrades and syncs across machines.

Why does the Dokploy CLI fail to connect to my panel?

The DOKPLOY_URL must be the panel root without the /api suffix, for example https://dokploy.example.com, because the CLI appends /api itself. Also verify the API key is valid by running dokploy project all --json.

What are the limitations of the official Dokploy CLI?

compose.update silently ignores serverId, which must be set at compose.create time. There is no single-env-var setter, and multi-step LMS workflows like sync-env-vars and clone-environment remain in the separate LMS CLI rather than this Skill.