WEBDANGER / DOCS / BUILD

Command line

Publish with the existing WEBDANGER project pipeline.

01

Use the repository CLI

These commands run from a WEBDANGER source checkout with dependencies installed. A public npm installation is not required or implied. Run pnpm webdanger help for the supported options.

  1. Run the repository CLI from an installed WEBDANGER source checkout.
  2. Use pnpm webdanger help to inspect supported commands.
02

Connect securely

Create a personal CLI token in Consol security settings. Supply it through WEBDANGER_API_TOKEN in your local environment, then run login. Keep it out of source files, screenshots and shell history.

  1. Create a personal CLI token in Consol security settings.
  2. Set WEBDANGER_API_TOKEN locally and run login; never paste the token into a project or public log.
03

Build, deploy, inspect

Build the site into dist before deploying. The CLI prints the project URL. Set --dir to your actual static output directory. Backend processes are not deployed by this static command.

  1. Create/select your project, build its static output and deploy that directory.
  2. Inspect status and deployments; keep the accepted deployment ID for a later rollback.

Run from the WEBDANGER source checkout. Supply your token through a local environment variable.

pnpm webdanger login
pnpm webdanger init --name "My website" --slug my-website
pnpm webdanger preview --dir dist
pnpm webdanger deploy --dir dist
pnpm webdanger status
pnpm webdanger deployments
pnpm webdanger rollback --to 1

WEBDANGER support.

Get help with your account, website, domain, billing or CARE offer.

contact@webdanger.com

The reply appears in this conversation. Email remains a fallback identity.