Move Deplo to another machine

Beta

Copy a whole Deplo, every team, account, app and database, to a fresh install on another machine. The old one keeps running.

Beta

This feature is currently beta/experimental and subject to change. It is not recommended for production. Try it out and share your feedback on our GitHub.

Move Deplo copies your whole Deplo onto another machine: a bigger box, another provider, or your own hardware. Everything comes across as it was:

  • every team, account, role, app, database, variable, domain and backup
  • each app's data, and the exact version it runs, with no rebuild
  • folders an app mounts from its server, except system and read-only ones (the progress page lists them)
  • API tokens and deploy hooks, which keep working

The old Deplo keeps running, untouched. You switch over when you are ready, one domain at a time.

Bringing only some teams?

Use Move from another Deplo: it brings teams into a Deplo that already runs others.

Before you start

CheckWhy
The new Deplo is a fresh installThe copy replaces everything on it: one account, no apps or databases. Servers you added are fine.
Both run the same versionUpdate the older one under Settings -> Deplo -> Updates.
The old Deplo has an https addressThe copy carries every secret, so it never runs over plain http.
The new Deplo has an addressSettings -> Deplo -> General -> Panel address.
The new Deplo has roomEvery app and database runs there too. Add servers to it first if one machine is not enough.

Move it

Install Deplo on the new machine

curl -fsSL https://deplo.build/install.sh | bash

Sign in and leave it empty. Add servers now if you want the apps spread over several.

Create a move code on the old Deplo

Settings -> Migrations -> Between Deplo -> This Deplo to another Deplo, then Create move code. The code starts with dmove_, is shown once, and expires after one hour if unused.

Connect from the new Deplo

Settings -> Migrations -> Between Deplo -> Another Deplo to this Deplo -> Everything. Enter the old Deplo's address, like https://deplo.example.com, and the dmove_ code.

Choose where everything lands

Every server of the old Deplo gets a server here to land on, this machine by default. Pick others to spread the load. Two databases with the same name on different old servers can't land on the same server: the review says so.

Start the move

Press Start move and confirm. The progress page shows Copy everything, then Deploy and copy data, then Finish.

Sign in again

The copy signs everyone out of the new Deplo. Sign in with your account from the old one; everyone else does the same.

Keep the progress page to yourself

Its address works without signing in, because the copy signs everyone out. Whoever has it can follow and retry the move. Once the copy is in, cancelling or finishing early needs an instance admin.

What the old Deplo notices

Almost nothing: it stays fully usable.

  • An app or database with data stops there only while its own data copies, then starts again. Meanwhile it can't be deployed or restarted. One without data never stops.
  • If the new Deplo stops answering mid-copy, the old one starts what it paused after a couple of minutes.
  • Changes made on the old Deplo after the copy started do not come across.

Switch over

Your domains still point at the old servers, so the old Deplo serves your traffic until you move them.

Point each domain at its new server

For example, change the A record of shop.example.com to the IP of the server it landed on. Deplo issues the certificate once the domain answers there.

Turn on schedules

The new Deplo starts with crons and scheduled backups paused, so nothing runs twice. Press Turn on in the banner once the new Deplo is the one you use.

Keep the panel's address, if you want

Point the old panel domain at the new machine and set it as the panel address. With a new address instead, passkeys must be set up again and webhooks changed.

Two Deplos, from now on

After the move, a change on one stays there.

  • API tokens, deploy hooks and members exist on both. A token revoked on one still works on the other.
  • Backups made before the move show on both, and the new Deplo never deletes them. Backups on a server's disk stay on the old server.
  • Pushes keep deploying on the old Deplo until you point the webhooks at the new one.

When you no longer need the old Deplo, uninstall it.

If something goes wrong

What you seeWhat to do
Some apps failed with a reasonFix it, then Try again. Only the failed and waiting ones run again.
One app keeps failingSkip it. The move finishes without it; add it again by hand.
You want to stopCancel move. The old Deplo starts what it paused; everything copied here is deleted and this Deplo goes back to setup.
The old Deplo is gone mid-moveFinish without the old Deplo. Apps whose data never came across are left out.
Needs an empty DeploMove into a fresh install, or bring only some teams instead.
The old Deplo runs an older versionUpdate it, then connect again.
This move code expiredCreate a new one on the old Deplo.
This move code is already in use by another DeploA code works for one new Deplo only. Create a new one.

Next steps

Did this page help you?

On this page