remote-rollback

Rollback the remote development environment to a previous Docker image version.

📋 TEMPLATE: This command is a template. Replace placeholders with your infrastructure values before use. See the Customization Guide at the bottom.

Workflow

1. Assess Current Situation

Get current problematic version:

# ┌─────────────────────────────────────────────────────────┐
# │ CUSTOMIZE: Replace with your SSH and container settings │
# └─────────────────────────────────────────────────────────┘
ssh -i {{SSH_KEY_PATH}} {{REMOTE_USER}}@{{REMOTE_HOST}} "docker inspect {{APP_CONTAINER_STAGING}} 2>/dev/null | grep 'org.opencontainers.image.revision' | cut -d'\"' -f4 || docker inspect {{APP_CONTAINER_DEV}} | grep 'org.opencontainers.image.revision' | cut -d'\"' -f4"

Check current status:

curl -s http://{{REMOTE_HOST}}:{{DEV_PORT}}/api/health 2>/dev/null || echo "Health check failed"

Document the issue for Linear ticket creation later.

2. List Available Rollback Targets

Show recent images on remote host:

ssh -i {{SSH_KEY_PATH}} {{REMOTE_USER}}@{{REMOTE_HOST}} "docker images {{REGISTRY}}/{{IMAGE_NAME}} --format 'table {{.Tag}}\t{{.ID}}\t{{.CreatedAt}}'"

Cross-reference with git commits to show messages:

git log origin/dev -10 --oneline

3. Select Rollback Target

If argument provided (commit SHA like e9722d4):

• Use specified commit as rollback target
• Verify image exists with that SHA tag

If no argument provided:

• Display last 5 available images with commit messages
• Recommend previous stable version (before current)
• Ask user to confirm selection

Default behavior: Select image before current (most common rollback scenario)

4. Pull Rollback Image

Pull the specific version from registry:

ssh -i {{SSH_KEY_PATH}} {{REMOTE_USER}}@{{REMOTE_HOST}} "docker pull {{REGISTRY}}/{{IMAGE_NAME}}:{{TAG_PREFIX}}-{target-sha}"

If image not in registry (old version pruned), use local cached image.