Skip to content

fcakyon/claude-codex-settings / plugins/dokploy-skills/skills/dokploy-deploy

dokploy-deploy

Flagged

This 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".

FileKindSize
SKILL.mdskill md3.6 KB
references/applications/advanced.mdxmarkdown13.8 KB
references/applications/build-type.mdxmarkdown9.0 KB
references/applications/going-production.mdxmarkdown7.0 KB
references/applications/index.mdxmarkdown4.3 KB
references/applications/meta.jsonconfig155 B
references/applications/preview-deployments.mdxmarkdown3.9 KB
references/applications/rollbacks.mdxmarkdown6.0 KB
references/applications/zero-downtime.mdxmarkdown2.9 KB
references/cli-commands.mdmarkdown34.3 KB
references/cloud/cloud.mdxmarkdown5.3 KB
references/databases/backups.mdxmarkdown1.3 KB
references/databases/connection/index.mdxmarkdown1.8 KB
references/databases/connection/mariadb.mdxmarkdown859 B
references/databases/connection/mongo-atlas.mdxmarkdown795 B
references/databases/connection/mysql.mdxmarkdown852 B
references/databases/connection/pg-admin.mdxmarkdown1020 B
references/databases/connection/redis.mdxmarkdown772 B
references/databases/index.mdxmarkdown4.3 KB
references/databases/restore.mdxmarkdown1.9 KB
references/docker-compose/domains.mdxmarkdown11.1 KB
references/docker-compose/example.mdxmarkdown4.1 KB
references/docker-compose/index.mdxmarkdown8.4 KB
references/docker-compose/utilities.mdxmarkdown2.6 KB
references/domains/cloudflare.mdxmarkdown6.5 KB
references/domains/generated.mdxmarkdown1.3 KB
references/domains/index.mdxmarkdown11.7 KB
references/domains/others.mdxmarkdown1.7 KB
references/getting-started/installation.mdxmarkdown8.9 KB
references/getting-started/manual-installation.mdxmarkdown16.8 KB
references/remote-servers/build-server.mdxmarkdown5.5 KB
references/remote-servers/deployments.mdxmarkdown1.4 KB
references/remote-servers/index.mdxmarkdown3.4 KB
references/remote-servers/instructions.mdxmarkdown4.4 KB
references/remote-servers/security.mdxmarkdown2.7 KB
references/remote-servers/validate.mdxmarkdown2.4 KB

references/applications/zero-downtime.mdx

View on GitHub
---
title: Zero Downtime
description: Learn how to configure zero downtime deployments in Dokploy.
---


Dokploy allows you to configure zero downtime deployments, which means that you can deploy your application without any downtime.

By default when you create a new deployment it will stop the latest running container and start the new one. This is the default behavior of Docker Swarm and this leads to Bad Gateway since
the containers are initializing at the same time,
but Dokploy allows you to configure zero downtime deployments.

## Steps to configure Zero Downtime Deployments

Let's suppose we have a NodeJS application that has a health check route `/health` that returns a 200 status code and running in the port 3000.

1. In your application is necessary to have a `Path` or `Health Route` to be able to achieve zero downtime deployments eg. in the case of a NodeJS app you can have a route `/health` that returns a 200 status code.
2. Go to `Advanced` Tab and go to Cluster Settings and enter to `Swarm Settings`
3. There are a couple options that you can use, in this case we will focus on `Health Check`.
4. Paste this code in the health check field:
Make sure the API Route exists in your application

```json
{
  "Test": [
    "CMD",
    "curl",
    "-f",
    "http://localhost:3000/health"
  ],
  "Interval": 30000000000,
  "Timeout": 10000000000,
  "StartPeriod": 30000000000,
  "Retries": 3
}
```

## Example

1. We will use this example [Github Repo](https://github.com/Dokploy/swarm-test)
2. It Have a endpoint called `health` [endpoint](https://github.com/Dokploy/swarm-test/blob/main/index.js#L20) which is the one that will tell us if our application is healthy.
3. For testing purpose I've added a sleep to simulate the delay between the deployments and you can see the bad gateway error.


1. **Use Git Provider in Your Application**:
   - Repository: `https://github.com/Dokploy/swarm-test`
   - Branch: `main`
   - Build path: `/`

If you want to test that there is no zero downtime yet, you can simply deploy the application and then create another deployment and while doing the deployment reload the page in the path /health and you will see that a bad gateway will appear.

Now go to the advanced section of our application, and go to the Swarm Settings section, we are going to modify the first section of Healtchecks.

We will use this configuration specifically, paste and save it

```json
{
  "Test": [
    "CMD",
    "curl",
    "-f",
    "http://localhost:3000/health"
  ],
  "Interval": 30000000000,
  "Timeout": 10000000000,
  "StartPeriod": 30000000000,
  "Retries": 3
}
```

This configuration basically tells to Docker to do:

Make a request inside the container to http://localhost:3000/health and then we are also saying to make in interval of 30000000000 nanosec, and also makes 3 retries before switching to the new container

that would be all, Now you have Zero Downtime Deployments 🎊.

writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deploymentStars: 322kUpdated Claude CodeCodexVerifiedInstall
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: 198kUpdated Claude CodeCodexVerifiedInstall
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: 119kUpdated Claude CodeCodexVerifiedInstall
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: 118kUpdated Claude CodeCodexVerifiedInstall