What problem will this feature address?
Currently, when a service or Docker Compose application is created under a project in Dokploy, there is no built-in way to move it to a different project without recreating it from scratch. This forces users to:
- Delete and redeploy the service/compose under the new project, causing downtime and potential configuration loss.
- Manually copy environment variables, volumes, networks, and other settings, which is error-prone and time-consuming.
- Lose deployment history, logs, and metrics associated with the service.
This limitation becomes especially problematic in team environments, where project structures evolve, services get reorganized, or when a service was initially placed in the wrong project due to experimentation or oversight.
Describe the solution you'd like
Introduce a "Move to Project" feature for services and Docker Compose applications, allowing users to transfer them from one project to another seamlessly. Key aspects of the solution:
- UI/CLI Action: Add a "Move" button in the service/compose detail view or context menu, prompting the user to select the target project.
- Preserve Configuration: All environment variables, volumes, networks, registry credentials, health checks, and deployment settings should be carried over.
- Zero Downtime: The service/compose should continue running during the migration. The process should update the project metadata in the database without restarting containers.
- Audit Log: Log the migration event in the service history for traceability.
- Validation: Check for naming conflicts in the target project and optionally allow renaming or prompt the user to resolve them.
- Bulk Move (Optional): Allow moving multiple services/composes at once to streamline restructuring.
This feature would improve project management flexibility and reduce operational overhead when reorganizing deployments.
Describe alternatives you've considered
No alternatives as of now.
Additional context
No response
Will you send a PR to implement it?
No
What problem will this feature address?
Currently, when a service or Docker Compose application is created under a project in Dokploy, there is no built-in way to move it to a different project without recreating it from scratch. This forces users to:
This limitation becomes especially problematic in team environments, where project structures evolve, services get reorganized, or when a service was initially placed in the wrong project due to experimentation or oversight.
Describe the solution you'd like
Introduce a "Move to Project" feature for services and Docker Compose applications, allowing users to transfer them from one project to another seamlessly. Key aspects of the solution:
This feature would improve project management flexibility and reduce operational overhead when reorganizing deployments.
Describe alternatives you've considered
No alternatives as of now.
Additional context
No response
Will you send a PR to implement it?
No