drift Docs
Pages
drift Docs
Start
What is Drift?
The tour, if you are new here.
Use cases
Whether Drift does your thing.
Getting started
Nothing to deployed, in one command.
Architecture
How a slice is put together.
What it costs
The free grant, four unit prices, two rules.
Moving off Azure
Estimate, snapshot and transform a resource group.
Build
Canvas
Static sites, same origin as your API.
Tools
Operate
Auth
Route gates, API keys and your account.
Teams
More than one person on one account.
Security
Boundaries, sandboxing and hardening.
Troubleshooting
Error codes
What went wrong, and what to do about it.
Legal
Acceptable use
What a slice may not be used for.
Data processing
The DPA, and every sub-processor.

CLI Reference

One page per noun, each with every verb, flag and output it carries. The binary's own three commands (drift, --version and upgrade) are on the CLI overview. The commands that act on a whole Driftfile (drift plan, drift apply and drift size) are on the drift file page, with the commands that work on the file itself.

The commands

Session

Your login lives in ~/.drift/session.json, one profile per account you're logged in to. It holds credentials only: the slice a command acts on comes from DRIFT_SLICE or the Driftfile you are standing in, never from the session. Every authenticated request carries:

  • Authorization: Bearer <jwt>, your identity
  • X-Slice: <active-slice>, the target slice

drift plan and drift apply name the slice from the Driftfile, so they act on it whichever slice is active. Tokens are refreshed automatically on a 401 that means the session expired. If the refresh fails, you're prompted to log in again. Account has the file's shape and how to work as more than one account, and Authentication has the token lifetimes.

Bare drift opens the terminal dashboard.

It runs over the same data with slices down the side, and Atomic / Backbone / Canvas panes for browsing functions, documents and sites.