Two Small Clouds

Control Dashboard

Signed out

Account

Setup status

0Sites
0Environments
0SSH keys
0Deploy tokens

Signed-in user

Operational next steps

  • Register a site, then add at least one environment.
  • Add an SSH key before launching infrastructure.
  • Create a deploy token and CI template for repeatable web-native deploys.
  • Use the CLI for local database, files, and project bundling tasks.

Sites

Registry

Environments

Runtime targets

Deployments

Status and rollback

Artifacts

Reusable code bundles

Deploy tokens

CI access

SSH keys

User access keys

CI templates

Web-native deployment


        


        

          

            

              
Local project companion

              
CLI-only coverage

            

          

          

            

              
Local setup

              
./tsc init
./tsc settings
./tsc setup

            

            

              
Local bundle flows

              
./tsc launch --environment Production
./tsc deploy --environment Production
./tsc restore --environment Production --sql ./site.sql.gz
./tsc sync-files --environment Production

            

            

              
Maintenance

              
./tsc clean --dry-run
./tsc version
./tsc update
./tsc install --bin-dir ~/.local/bin

            

            

              
Why these stay local

              
These commands inspect or modify the Drupal checkout, local config, generated artifacts, or installed launcher. The hosted dashboard keeps those actions visible but leaves filesystem work in the CLI.