Home/Docs/CLI Commands

CLI commands

TurboCI keeps the operational surface small.

Bootstrap the config, push a deployment, target or skip specific services, and inspect the live fleet from the same CLI.

5 core commands

cover bootstrap, deploy, teardown, inspection, and provider specs

Target / skip

scope updates to the exact services or deployments you need

flow

bash

turboci init
turboci up
turboci control

Core commands

The commands you will use most often

Deploy

turboci up

Reads `.turboci/config.yaml`, creates missing infrastructure, and updates existing deployments in place. If no configuration is found, TurboCI falls back to `turboci init`.

command

bash

turboci up

Bootstrap

turboci init

Creates or updates the configuration interactively so you can define the deployment without hand-writing the file first.

command

bash

turboci init

Teardown

turboci down

Destroys resources created by TurboCI. Targeting and skipping work at the deployment level here, not the service level.

command

bash

turboci down
turboci down -t deployment_name

Inspect

turboci control

Opens an interactive management surface for active deployments, including SSH access into the running fleet.

command

bash

turboci control

Reference

turboci spec

Lists provider-specific locations, server types, and operating system options so you can size deployments correctly.

command

bash

turboci spec

Targeting

Deploy only the services you specify

Use `-t` or `--target` to limit the rollout to one service, many services, or whole deployment groups.

targeting

bash

turboci up -t deployment_name.service_name
turboci up -t deployment_name.service_name -t deployment_name.service_name_2
turboci up -t "deployment_name.*"
turboci up -t service_name -t service_name_2

Omitting the deployment name lets TurboCI match the service name anywhere it appears.

Skipping

Exclude services without rewriting the config

Use `-s` or `--skip` to leave specific services untouched while everything else deploys.

skipping

bash

turboci up -s deployment_name.service_name
turboci up -s deployment_name.service_name -s deployment_name_2.service_name
turboci up -s "*.*"

Skipping *.* leaves only the default deployment infrastructure in place.

Common workflows

A few operator shortcuts worth keeping nearby

workflows

bash

# Deploy everything
turboci up

# Update only the web service
turboci up -t deployment_name.web

# Deploy every service in a specific deployment
turboci up -t "production.*"

# Tear down one deployment
turboci down -t deployment_name

Next step

Wire the CLI to your provider credentials

The next piece is environment-based provider authentication, so TurboCI can resolve the correct cloud credentials for each deployment.

Continue to environment variables