Managing Multiple Breezes Efficiently

When to Use Multiple Servers

• Isolation — separate production from staging/development
• Security — isolate sensitive applications (payment processing, user data)
• Performance — dedicated database server for heavy workloads
• Scaling — distribute load across multiple servers

Organization Tips

• Name Breezes descriptively: prod-web-01, staging-api, db-primary
• Document each server's purpose and what runs on it
• Keep an inventory spreadsheet with IPs, purposes, and owners

Centralized Management

# Use SSH config for easy access
# ~/.ssh/config
Host prod-web
    HostName 198.51.100.10
    User deploy

Host staging
    HostName 198.51.100.20
    User deploy

Host db-primary
    HostName 198.51.100.30
    User deploy

Automation

# Run command on all servers
for host in prod-web staging db-primary; do
    echo "=== $host ==="
    ssh $host "uptime && df -h /"
done

Cost Management

• Use the smallest plan that meets each server's needs
• Destroy staging servers when not actively testing
• Consider consolidating low-traffic sites onto one server