The CLI works against one **cloud project** at a time. This page covers how the link between your local folder and that project works, how to select a project, a...
The CLI works against one **cloud project** at a time. This page covers how the link between your local folder and that project works, how to select a project, a...
The CLI works against one cloud project at a time. This page covers how the link between your local folder and that project works, how to select a project, and how to jump into the app from your terminal.
How the link works
When you run dxb init, it links your folder to a cloud project by writing .doxbrix/config.json:
{
"projectId": "bc7bf459-3d54-4b1a-be18-393c61567633",
"projectSlug": "my-docs",
"basePath": "docs"
}.doxbrix/config.json to Git so your whole team is linked automatically after cloning — it contains no secrets (authentication uses tokens).Select a project
Choose which project commands act on:
# List the projects you can access
dxb project list
# Inspect one
dxb project view my-docs
# Set the selected project for this folder
dxb project use my-docsYou can also target a project per-command with -p / --project, or set the DOXBRIX_PROJECT environment variable — see Authentication.
Open the app or editor
Jump from the terminal into the web app:
# Open the dashboard / app
dxb open
# Open the editor for the selected project
dxb open editordxb open takes an optional target — app (default) or editor.
Sharing unpublished docs
There's no hosted preview-link command in the CLI. To share work-in-progress:
- Preview locally with
dxb dev. - Or use the app's Preview, controlled by the Preview access rule (Workspace members, Project members, or Anyone with link).