dbdock sync

npx dbdock sync [status|push|pull] [options]

Mirrors this project’s configuration metadata to your DBDock Cloud dashboard. With no action, sync pushes local changes. For the concepts and workflow, see Syncing a project.

Only non-secret metadata is uploaded — passwords, keys, and webhook URLs stay local. See Data handling.

Prerequisites

Signed in with dbdock login
Project linked with dbdock init

Actions

Action	Description
`dbdock sync`	Push local metadata to the cloud (default).
`dbdock sync status`	Compare local vs. cloud — revisions, pending changes, last sync.
`dbdock sync pull`	Adopt the cloud baseline as your local starting point.

Options

Option	Description
`--force`	Overwrite cloud state with local. Resolves a conflict in favor of your machine.

Examples

dbdock sync
# → Synced. 1 change set(s) pushed.

dbdock sync status
# Project:  proj_...
# Local:    revision 7
# Cloud:    revision 7
# In sync.

dbdock sync --force

Conflicts

If the cloud has diverged from the baseline your machine last saw, sync stops and exits 1 rather than guess:

Cloud has diverged from your local baseline (conflict).
Resolve with `dbdock sync pull` (adopt cloud) or `dbdock sync --force` (overwrite cloud).

Conflict snapshots are saved under .dbdock/conflicts/ so nothing is lost while you decide.

Exit codes

Code	Meaning
`0`	Synced, or already up to date
`1`	Conflict, not authenticated, or no linked project

dbdock open

Jump to this project in the dashboard.

Cloud Sync overview

The full picture.

dbdock login dbdock open

CLI

Cloud Sync (CLI)

Storage Providers

Migration

Alerts & Automation

Prerequisites

Actions

Options

Examples

Conflicts

Exit codes

dbdock open

Cloud Sync overview

​Prerequisites

​Actions

​Options

​Examples

​Conflicts

​Exit codes

​Related

dbdock open

Cloud Sync overview

Prerequisites

Actions

Options

Examples

Conflicts

Exit codes

Related