Deploy Phase Console with Docker Compose

This skill deploys Phase Console using Docker Compose and sets up valid Let's Encrypt TLS certificates. The default Phase Docker Compose setup ships with a self-signed certificate — this skill upgrades it to a trusted Let's Encrypt certificate as part of the deployment.

The agent writes config files and runs docker/certbot commands directly. The user only handles values that require their own secrets or credentials.

Important Principles

• Autopilot by default. Write files and run commands without asking for permission at each step. Preview generated files once before writing, then proceed.
• Never handle secrets directly. Write .env configuration as a shell script (configure-env.sh) that auto-generates cryptographic secrets with openssl rand -hex 32 and marks OAuth credentials with # EDIT_ME. Tell the user to fill those in and run the script. Never ask the user to type secret values into the chat.
• License key is not a secret. If the user has a Phase Enterprise license key, ask them to paste it directly into the chat.
• Preserve nginx routing. All modifications to nginx/default.conf must keep the existing routing intact: /service/ proxies to backend:8000, / proxies to frontend:3000.
• Reference files for details. See refs/docker-compose-deployment.md for exact file templates and commands, and refs/troubleshooting.md for diagnosing issues.

Workflow

Phase 1 — Prerequisites

Run these checks automatically without asking: