fcakyon/claude-codex-settings / plugins/dokploy-skills/skills/dokploy-deploy
dokploy-deploy
FlaggedThis skill should be used when user asks to "deploy with Dokploy", "use Dokploy Cloud", "manage self-hosted Dokploy", "deploy Docker Compose on Dokploy", "manage Dokploy databases", "configure Dokploy domains", or "look up Dokploy CLI commands".
references/remote-servers/validate.mdx
View on GitHub---
title: Validate
description: "Validate your remote server deployment"
---
import { Callout } from 'fumadocs-ui/components/callout';
Dokploy validates different components depending on the type of remote server you're configuring. The validation requirements differ between **Deployment Servers** and **Build Servers**.
## Deployment Servers
For **Deployment Servers**, Dokploy requires the following 7 components to be properly configured:
1. **Docker Installed**: Docker must be installed on the remote server.
2. **RClone Installed**: RClone must be installed on the remote server.
3. **Nixpacks Installed**: Nixpacks must be installed on the remote server.
4. **Railpack Installed**: Railpack must be installed on the remote server.
5. **Buildpacks Installed**: Buildpacks must be installed on the remote server.
6. **Docker Swarm Initialized**: Docker Swarm must be initialized on the remote server.
7. **Dokploy Network Created**: A Docker network for Dokploy must be created on the remote server.
8. **Main Directory Created**: A directory must be created on the remote server to store applications.
<Callout type="info">
Deployment servers are used to run and host your applications. They require Docker Swarm and network configuration since they need to run containers and manage deployments.
</Callout>
## Build Servers
For **Build Servers**, Dokploy only validates the following components:
1. **Docker Installed**: Docker must be installed on the remote server.
2. **RClone Installed**: RClone must be installed on the remote server.
3. **Nixpacks Installed**: Nixpacks must be installed on the remote server.
4. **Railpack Installed**: Railpack must be installed on the remote server.
5. **Buildpacks Installed**: Buildpacks must be installed on the remote server.
6. **Main Directory Created**: A directory must be created on the remote server to store applications.
<Callout type="info">
Build servers are dedicated to building and compiling applications. They don't require Docker Swarm or network configuration since they only build images and push them to a registry, without running any containers.
</Callout>
## Validation Status
Once all requirements are met for your server type, you will see a green checkmark next to each item in the validation section.
<ImageZoom
src="/assets/images/server-validate.webp"
alt="Multi-Server Setup"
width={1000}
height={600} />Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deployment | Stars: 321k | Updated | Claude CodeCodex | Verified | Install |
| xlsxanthropics/skillsUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved. | Stars: 197k | Updated | Claude CodeCodex | Verified | Install |
| shipping-and-launchaddyosmani/agent-skillsPrepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy. | Stars: 119k | Updated | Claude CodeCodex | Verified | Install |
| childhoodthedotmack/claude-memBabysit a shipped release after merge, publication, or deployment. Verify published packages, production behavior, installed plugins, and late CI or user reports until the observation window is clean; use babysit for PR readiness before release. | Stars: 118k | Updated | Claude CodeCodex | Verified | Install |