Dokploy production deployments

Use this skill for changes that affect a Dokploy production deployment, deployment failures, or post-deploy verification. Apply the general Docker and Dokploy practices in docker-dokploy and the production-change safeguards in production-change alongside the target project's requirements.

Triggers

• A change affects a production deployment managed by Dokploy and Docker Compose.
• A Dokploy deployment fails or needs post-deploy verification.
• The user asks about production routing, service configuration, or persistent deployment data in a Dokploy-managed project.

Workflow

Before changing deployment configuration

1. Read the target repository's root AGENTS.md, deployment documentation, and production Compose file.
2. Inspect git status and preserve unrelated worktree changes.
3. Confirm the project's intended production deployment target and workflow. Do not reintroduce retired scripts, host-managed proxies, duplicate production Compose files, or alternate deployment targets.
4. Identify credentials and secret files used by the deployment. Keep them out of Git, logs, command output, and chat; never print secret contents.
5. Identify persistent data paths and preserve them unless the user explicitly requests a data migration.