Secrets stay on your machine. Sync uploads only non-sensitive metadata. Database passwords, storage keys, encryption secrets, and webhook URLs are never sent. See Data handling.
Why link them
Best of both
Script and automate locally; monitor, share, and review from a managed dashboard.
One source of truth
Your
dbdock.config.json stays authoritative. The dashboard mirrors it.Team visibility
Give teammates a read on what’s configured without sharing your machine.
Safe by design
Metadata-only sync means linking a project never exports a credential.
How it works
DBDock keeps a small.dbdock/ folder in your project that records which cloud project this directory is linked to and the last state it synced. Running dbdock sync compares your local config to the cloud baseline and pushes the differences.
1
Sign in
Run
dbdock login to authenticate to DBDock Cloud in your browser.2
Link the project
Run
dbdock init — it offers to link this directory to a cloud project. (Already have a config? It links the existing one.)3
Sync
Run
dbdock sync to push your local metadata to the dashboard. Use dbdock open to jump to it in the browser.Everyday commands
Next
Authentication
Sign in, profiles, and tokens.
Syncing a project
Push, pull, status, and conflicts.