Dokploy / Dokploy/dokploy

Import/Export dokploy projects

Open
#1,733 2 comments 40 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement
Dominant language
TypeScript
Stars
37.4k
Forks
3k
Avg merge
1d 3h
Merged PRs (30d)
73

Description

What problem will this feature address?

Currently, there is no built-in way to export a Dokploy project configuration and re-import it into another instance.
This presents a challenge for:

  • Backup & recovery workflows — there's no way to version control or archive project configs.
  • Migration across environments — users cannot easily replicate staging → production setups.
  • Sharing reusable setups — templates and starter kits cannot be distributed without manually recreating each element.

This limits the portability, reproducibility, and collaboration potential of Dokploy-managed projects.

Describe the solution you'd like

Add functionality to:

  1. Export a Dokploy project (apps, environments, secrets, volumes, domains, etc.) to a standardized portable format (e.g., JSON or YAML).
  2. Import a project from such a file into any other Dokploy instance, with options for:
    • overwriting existing project with the same name,
    • skipping conflicting items,
    • dry-run/preview mode.
Describe alternatives you've considered

Just import/export as json

Additional context

No response

Will you send a PR to implement it?

No

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No files, tests, or entry points are named in the issue. Start by tracing how Dokploy represents projects and their apps, environments, secrets, volumes, and domains, then review existing JSON handling before defining the portable format and conflict behavior. Done means export, import, overwrite/skip handling, and dry-run behavior are specified and covered by tests.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
devops
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.