Skip to content

Install the CLI ​

The edge CLI does everything the HTTP API does, from a terminal or a script. By the end of this page you will have installed it, signed in, and published a folder as a preview deployment.

You need a DECA Cloud account in an organization with Edge enabled, and a folder with an index.html in it. This page uses an existing distribution, acme-marketing. If you do not have one yet, create it first with Publish your first site.

1. Install ​

bash
curl -fsSL https://cli.edge.deca-dev.com/install.sh | sh
powershell
irm https://cli.edge.deca-dev.com/install.ps1 | iex
bash
brew install resola-ai/tap/deca-edge
edge profile use edge.deca-dev.com

The install script downloads one binary for your platform, checks it against the published checksum, and puts it on your PATH. It also points the CLI at this environment, which is why the Homebrew route needs the extra profile use line.

Check it worked:

bash
edge version
text
edge 0.1.6 (c8ca7f4, 2026-10-24)

2. Sign in ​

bash
edge login
text
Opened the sign-in page in your browser…
✓ Signed in as kenji@acme.example (organization acme, workspace default)

Complete the browser sign-in and pick your organization when Auth0 asks. The CLI waits on a loopback callback and finishes on its own. Organization membership is what attaches Edge roles to the token, so do not skip that step.

On a machine without a browser (SSH, remote container), use edge login --device for a one-time code. That path cannot carry organization roles on Auth0 today, so prefer the default browser login when you can.

Your sign-in is stored in the system keychain. Check who you are and what you can do:

bash
edge whoami
text
api_url          https://api.edge.deca-dev.com
expires_at       2026-10-10T10:12:44Z
organization_id  acme
profile          edge.deca-dev.com
scopes           ["deployment.promote","deployment.read","deployment.write","distribution.read"]
token_source     keychain
workspace_id     default

From the project folder:

bash
edge link --distribution acme-marketing --dir dist
text
✓ Linked to acme-marketing (d3f7a1c4-90b2-4e6a-8f15-6c2b7e0a9d38)
  wrote .edge/project.json

The link file holds the distribution id and the folder to publish. It has no secrets, so you can commit it and your teammates get the same target.

4. Publish a preview ​

bash
edge deploy
text
Packing dist/ → bundle.tar.gz (14 files, 212 KB)
Created deployment 01M4A7Q2XKJ9T3VN6P8RWS5BCD
Uploaded
Committed — waiting for the preview…
✓ ready
Preview  https://01m4a7q2xkj9t3vn6p8rws5bcd.preview.edge.deca-dev.com
The live site is unchanged. Promote with: edge deployments promote 01M4A7Q2XKJ9T3VN6P8RWS5BCD

edge deploy runs the whole publish flow: it packs the folder as a .tar.gz with your files at the root, creates a deployment, uploads, commits, and waits until the preview is ready.

This does not change the live site. Open the preview URL and check it. If the preview returns 404 for a few seconds, wait and reload; the preview is still reaching every edge location.

5. Promote it ​

When the preview looks right:

bash
edge deployments promote 01M4A7Q2XKJ9T3VN6P8RWS5BCD
text
Promote 01M4A7Q2XKJ9T3VN6P8RWS5BCD to https://acme-marketing.edge.deca-dev.com? [y/N] y
✓ Live  https://acme-marketing.edge.deca-dev.com

This is the step that changes what visitors see. It is not one-way: edge deployments rollback --distribution acme-marketing puts the previous deployment back. See Patch, promote, and roll back.

Once you trust the flow, edge deploy --promote does steps 4 and 5 in one go.

Next ​