Skip to main content
Before you can sync, the CLI needs to know who you are. DBDock uses browser-based OAuth — the same secure sign-in as the dashboard — so there’s no long-lived API key to create or store in plaintext.

​
Sign in

This opens your browser to authorize the CLI. Once you approve, DBDock stores your credentials locally and confirms the account:
If the browser doesn’t open automatically, the CLI prints a URL you can visit manually. Credentials are saved under your DBDock home directory (~/.dbdock/), not in your project.

​
Check who you are

​
Sign out

Removes the stored credentials for the active profile. Your project’s .dbdock/ link is left untouched — sign back in later and continue.

​
Tokens for CI

Interactive browser sign-in isn’t available in automation. For CI, provide a token instead:
Treat DBDOCK_TOKEN like any other secret — inject it from your CI provider’s secret store, never commit it. See Key management.

​
Multiple accounts with profiles

If you work with more than one DBDock account (say, personal and work), use profiles:
Each profile stores its own credentials and API endpoint. Commands use the default profile unless you pass --profile.

​
Organizations

Organizations are forward-compatible — accounts are single-scope today, and this command sets a value for when multi-org support ships. You can safely ignore it for now.

​
Environment variables

A token to authenticate with instead of the browser flow. Useful in CI.
Override the API endpoint. Defaults to https://api.dbdock.xyz/api/v1.
Override the dashboard URL used by dbdock open. Defaults to https://dbdock.xyz.
Where global credentials and config live. Defaults to ~/.dbdock.

​
Next

Sync a project

Now that you’re signed in, push your project to the cloud.