Skip to main content

tly start

Overview​

The tly start command wakes a sleeping deployment and makes it active again, without requiring a full redeployment.

Usage​

tly start <deployment-id>

Arguments​

ArgumentDescriptionRequired
deployment-idID of the deployment to wakeYes

How It Works​

Targetly automatically puts idle deployments to sleep to save resources. When you run tly start:

  1. Targetly starts the stopped Docker container
  2. The deployment becomes active at its original URL
  3. No rebuild or configuration changes needed
info

Unlike redeploying, tly start preserves the exact same container image and configuration from the original deployment.

Examples​

Basic Usage​

tly start abc123def456

Output:

🚀 Starting deployment abc123def456...
✓ Container started successfully

━━━━━━━━━━━━━━━━━━━━━━━━
📋 ID: abc123def456
🌐 URL: https://abc123def456.prod.targetly.io
📊 Status: Running
━━━━━━━━━━━━━━━━━━━━━━━━

Start and View Logs​

tly start abc123def456 && tly logs abc123def456

When to Use​

Use tly start when:

  • ✅ Your deployment has automatically gone to sleep due to inactivity
  • ✅ You manually stopped a deployment with tly stop
  • ✅ You want to resume without making code changes

Don't use tly start when:

  • ❌ You've made code changes (use tly deploy instead)
  • ❌ You need to update environment variables (redeploy required)
  • ❌ The deployment doesn't exist (deploy first)

  • tly stop Put a deployment to sleep

  • tly list See which deployments are sleeping

  • tly logs Monitor deployment after waking

Troubleshooting​

Deployment not found

Error: Error: deployment abc123 not found

Solution: Use tly list to find the correct deployment ID.

Already running

Message: Deployment is already running

The deployment is already active. No action needed.

Start failed

Error: Failed to start container

Solutions:

  • Check logs: tly logs <deployment-id>
  • Redeploy if container is corrupted: tly deploy