deploy

Deploy the AI Poker Wizard bot to production with Docker Compose and Supabase migrations.

7|2|Updated Feb 13, 2026
One-click install
npx skills add https://github.com/a00012025/ai-poker-wizard --skill deploy-a00012025
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: deploy
Source: https://github.com/a00012025/ai-poker-wizard/tree/main/.claude/skills/deploy
Command: npx skills add https://github.com/a00012025/ai-poker-wizard --skill deploy-a00012025

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Deploying, updating, and troubleshooting the AI Poker Wizard bot involves many manual steps, environment configurations, and database migrations, making the process error‑prone and time‑consuming.

Core Features & Use Cases

  • Automated regression testing before every deployment to ensure stability.
  • Integrated Supabase migration handling so database schema stays in sync.
  • Docker Compose orchestration that rebuilds containers, applies graceful shutdowns, and restarts services automatically.
  • Step‑by‑step verification of container health, logs, and database connectivity.
  • Troubleshooting guidance for common startup failures such as missing tables or connection issues.
  • Use case: A developer can confidently push new bot features, run the deploy script, and have the updated bot running with minimal manual intervention.

Quick Start

Run the deploy script by executing bash scripts/deploy.sh once the .env file and token files are prepared.

Frequently Asked Questions about deploy

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate Docker container deployment and Supabase migrations together?

Automated Docker Compose deployment orchestrates container rebuilds, applies graceful shutdowns, and restarts services while integrating Supabase CLI migrations to keep the database schema synchronized during production updates.

What's the best way to troubleshoot a bot container that fails to start after deployment?

Troubleshooting a failed bot container startup involves step-by-step verification of container health, reviewing Docker logs, and checking database connectivity to resolve common issues like missing tables or connection failures.

Do I need to run regression testing before deploying updates to production containers?

Regression testing runs automatically before every deployment to ensure stability, verifying that new bot features and container updates will function correctly in the production environment before applying any changes.

What environment setup is required before running an automated Docker and Supabase deployment script?

Running an automated deployment script requires a configured .env file, necessary token files, Docker, Docker Compose, and Supabase CLI installed to apply migrations and successfully start services.

Can I use Docker Compose to gracefully restart bot containers without dropping database connections?

Docker Compose orchestration applies graceful shutdowns and restarts services automatically, managing container rebuilds while verifying container health and database connectivity to maintain stability during updates.

Why does my database migration fail when deploying the bot with Supabase CLI?

Supabase CLI database migration failures during bot deployment typically stem from missing tables or connection issues, requiring step-by-step verification of database connectivity and container health to resolve.