Once your cloud environment is set up, here's how to use it day-to-day.
./ds cloud-dev start
Wait for the instance to be running:
./ds cloud-dev list
./ds cloud-dev ssh
# Or use the configured alias:
ssh devstride-yourname
cd ~/dev/devstride
git pull # Get latest changes
./ds run backend # Start backend server
In a second terminal (or tmux):
./ds run ui # Start frontend
Run commands on your cloud instance from your local terminal:
# Start/stop services
./ds cloud-dev start-backend # Start backend (./ds run backend)
./ds cloud-dev stop-backend # Stop backend process
./ds cloud-dev start-frontend # Start frontend (./ds run ui)
./ds cloud-dev stop-frontend # Stop frontend process
# Database operations
./ds cloud-dev run-migrations # Run database migrations
./ds cloud-dev reset-database # Reset database from source
Stop your instance to save costs:
./ds cloud-dev stop
Your data is preserved on the EBS volume. When stopped, you only pay for storage (~$8/month).
# List all your instances
./ds cloud-dev list
# Get connection info
./ds cloud-dev info
Create additional instances for different work:
./ds cloud-dev create -i 2 # Creates devstride-dev-yourname-2
./ds cloud-dev ssh -i 2 # Connect to instance 2
./ds cloud-dev stop -i 2 # Stop instance 2
Remote-SSH: Connect to Hostdevstride-yourname (automatically configured)/home/ec2-user/dev/devstrideClaude Code is pre-installed on your instance:
# First time: authenticate
claude
# Then use normally
claude "explain this function"
The SSH config is automatically set with keepalive settings, but if you experience disconnects, add to your local ~/.ssh/config:
Host devstride-*
ServerAliveInterval 60
ServerAliveCountMax 3
# Start a named session
tmux new -s dev
# Detach: Ctrl+B, then D
# Reattach:
tmux attach -t dev
# On the instance
pkill -f 'sst dev' && ./ds run backend