Docs / CLI

A CLI-first path for Drupal teams who like clear commands.

The dashboard is useful, but the CLI keeps local development, deployment and hosted operations close to the codebase.

First useful run

Initialise a project, register a site and launch a Drupal environment.

./tsc setup
./tsc site register --name "Community site"
./tsc env add --name Production --profile drupal-basic
./tsc launch --environment Production --sql ./site.sql.gz

CI deployment

Create a deploy token and generate a provider-specific template.

./tsc deploy-tokens create --environment Production
./tsc ci-template --provider github-actions --environment Production
./tsc deploy --environment Production

Operations

Check hosted status, run Drush and write local Drush aliases.

./tsc status
./tsc drush --environment Production status
./tsc drush-aliases write --all

Backups and rollback

Use dashboard tasks during beta, with CLI coverage expanding around real pilot needs.

./tsc online deployments list --environment Production --json
./tsc online deployments rollback dep-abc123 --environment Production --yes

Find the next command

Use the CLI from setup through routine operations.

Commands stay organised around sites, environments, deployments and hosted tasks. Start with status when you need orientation, then use command help for the available options and output formats.