Skip to main content
Once you’re signed in and the project is linked, dbdock sync keeps your dashboard in step with your local configuration.

​
Push local changes

This reads your dbdock.config.json, compares it to the last synced state, and pushes the differences to DBDock Cloud.
If nothing changed, it says so and does nothing:
Only non-secret metadata is sent. See exactly what leaves your machine in Data handling.

​
Check status

Status works offline too — if the cloud is unreachable it reports unreachable (offline) and shows your pending local changes so you know what will push once you’re back online.

​
Pull the cloud baseline

Adopts the current cloud revision as your local baseline. Use it to align a fresh checkout, or as one side of resolving a conflict.

​
Resolving conflicts

A conflict means the cloud has diverged from the baseline your machine last saw — for example, the project changed from another machine. dbdock sync stops rather than guess:
You choose which side wins:

Keep cloud

Adopt the cloud state as your new baseline, then re-apply local changes if needed.

Keep local

Overwrite the cloud with your local metadata.
DBDock saves conflict snapshots under .dbdock/conflicts/ so nothing is lost while you decide.

​
Open the dashboard

Opens this project in the DBDock dashboard. To print the URL instead of launching a browser (handy over SSH):
dbdock open needs a linked project. If you see “No linked project,” run dbdock init first to link this directory.

​
Offline and retries

Sync is resilient. Change sets are queued locally and drained to the cloud; if a push fails, it’s retried on the next sync. dbdock sync status shows pending items and flags any that need attention.

Data handling

What syncs, and what never does.

dbdock sync reference

Command flags and exit codes.