feat: add remote service migration

[DenisHoppe]

Summary

• add remote project duplication and two-phase Application moves with explicit source cleanup
• add full-data Compose and PostgreSQL/MySQL/MariaDB/MongoDB/Redis/LibSQL moves using streamed transfers
• persist migration phases and owned artifacts for safe retry, rollback, collision prevention, source preservation, and deletion guards
• support local and remote monitoring consistently
• reject unsafe bind/anonymous/external mount scenarios and require explicit cleanup

This port is based directly on the remote migration work from a1dfb1a7f, 070de6adc, and 6f0195a5e, adapted to current Canary APIs. It is independent of AutoDNS, does not include the AutoDNS commits, and does not depend on codex/autodns-provider.

Related context: DenisHoppe/dokploy#1 and DenisHoppe/dokploy#2.

Validation

• pnpm --filter @dokploy/server typecheck
• pnpm --filter dokploy typecheck
• Biome check on all changed TypeScript/TSX/JSON files
• focused migration suite: 13 files, 98 tests passed
• locally executable full suite: 110 files, 982 tests passed
• full suite: 981 passed, 1 skipped; 5 environment-dependent tests could not run because Docker and Nixpacks are unavailable locally

Greptile Summary

This PR adds durable, two-phase remote moves for Compose and managed database services, including streamed data transfer, target collision protection, explicit finalization, rollback, and dashboard controls.

• Adds migration records and phase/ownership metadata for retry and cleanup.
• Streams Compose directories and persistent volumes between local or remote servers.
• Adds move, rollback, and finalize APIs and corresponding dashboard workflows.
• Extends local/remote monitoring behavior and guards conflicting service operations.

Confidence Score: 3/5

The PR should not merge until migration recovery cannot lose track of ownership changes or newly created target artifacts.

Separate writes can leave service placement inconsistent with migration state after interruption, while unrecorded target volumes or directories survive rollback and block safe retries.

Files Needing Attention: packages/server/src/services/compose-move.ts, packages/server/src/services/database-move.ts, packages/server/src/utils/migration/transfer.ts

_{Reviews (1): Last reviewed commit: "feat: add remote service migration" | Re-trigger Greptile}

Greptile also left 2 inline comments on this PR.

Context used (3)

• Knowledge Base — Managed data services
• Knowledge Base — Managed databases and storage
• Knowledge Base — Infrastructure runtime

[greptile-apps]

Ownership state diverges

If the process exits or the progress write fails after serverId is updated, ownershipMoved remains false, so rollback restarts the workload on the source without restoring its record from the target. The migration row is then deleted, leaving Dokploy managing the wrong server while an orphaned workload runs on the source. The database move at database-move.ts:402-410 has the same split write.

Knowledge Base Used:

• Managed data services
• Managed databases and storage

[greptile-apps]

Artifact ownership is lost

If the process exits or onTargetCreated fails after the target volume is created, its name is never persisted and this helper does not remove it. Recovery therefore omits the volume, which can contain partial data and blocks later migrations at the collision check; the directory path at line 154 has the same gap.

Knowledge Base Used: Managed databases and storage