Skip to content

feat(servers): add cross-instance server migration - #11075

Open
andrasbacsai wants to merge 2 commits into
nextfrom
server-migration-between-instances
Open

feat(servers): add cross-instance server migration#11075
andrasbacsai wants to merge 2 commits into
nextfrom
server-migration-between-instances

Conversation

@andrasbacsai

Copy link
Copy Markdown
Member

Summary

  • Add API endpoints to export, import, claim, and one-shot migrate servers (and hosted resources) between Coolify instances
  • Transfer bundles support sensitive data, optional passphrase encryption, adopt mode, UUID preservation, and Sentinel rebinding
  • After migration, disable automations on the source instance and block revalidation of transferred servers
  • Add multi-instance local dev tooling (scripts/dev-instances, docker-compose.dev-multi.yml) for testing server handoff between control planes

Breaking Changes

None.

Block source-side validation and force-enabling after transfer.
Commit claim metadata and Sentinel rebinding atomically, and mark the
source transferred only after the target import succeeds.
@gitguardian

gitguardian Bot commented Jul 28, 2026

Copy link
Copy Markdown

⚠️ GitGuardian has uncovered 1 secret following the scan of your pull request.

Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.

🔎 Detected hardcoded secret in your pull request
GitGuardian id GitGuardian status Secret Commit Filename
35244461 Triggered Generic Password 020238c app/Http/Controllers/Api/ServerTransferController.php View secret
🛠 Guidelines to remediate hardcoded secrets
  1. Understand the implications of revoking this secret by investigating where it is used in your code.
  2. Replace and store your secret safely. Learn here the best practices.
  3. Revoke and rotate this secret.
  4. If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.

To avoid such incidents in the future consider


🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant