Moving and exporting projects
Move a whole project to another server, or export it to a file and import it elsewhere.
A project lives on one server, but it is not stuck there. You can move it — applications, databases and volume data — to another server in your fleet, or export it to a file and import it on a different DockBoard instance.
Moving to another server
Available in multi-server mode. On the project page, open the server card, click the move button, pick the target server and confirm.
What DockBoard then does, in order:
- 01Tears down the applications and databases on the source server. Failures here do not block the move, and source volumes are kept on the old server.
- 02Reassigns the project to the target server.
- 03Transfers the Docker volumes asynchronously — exported on the source, imported on the target.
- 04Deploys the applications and databases on the target once the data has arrived, so the containers come up on real data rather than empty disks.
- 05Regenerates the reverse proxy so the domains follow the project.
What to expect
- There is downtime. The applications are unavailable while the volumes transfer and the stack redeploys on the new server.
- Volume discovery follows the platform naming convention. A stack that declares differently-named volumes is not covered when the source is a remote server.
- The target server must be
ONLINE. - An application running on a cluster cannot be moved to a single server — its placement *is* the cluster. Change cluster, or move it back to a single host first.
Exporting and importing
Moving is for machines you own in one DockBoard. Export is for crossing that boundary: a project’s definition — applications, their sources and ports, databases, environment variables, domain attachments — written to a file you can import elsewhere.
On import, review what the file declares before deploying: the target instance may have different servers, different domains and different quotas.