fizz-production

Enables Copilot to SSH into the Fizz EC2 instance and manage Docker containers for the fyzz.dev production app.

⭐3stars🔀0forks📁View on GitHub🕐Updated Jan 7, 2026⬇️1downloads

When & Why to Use This Skill

This Claude skill enables seamless management of production environments on AWS EC2 through automated SSH and Docker orchestration. It provides a comprehensive suite of tools for monitoring container health, analyzing real-time logs, and executing remote DevOps commands, significantly reducing the time required for infrastructure maintenance and incident response.

Use Cases

  • Real-time Production Monitoring: Use commands like Get-FizzHealth and Get-FizzStats to monitor the status of Next.js apps, PostgreSQL databases, and background workers.
  • Rapid Incident Troubleshooting: Quickly access and tail logs from specific containers (e.g., worker-discovery or app) to identify and debug production errors as they happen.
  • Automated Container Management: Perform remote operations such as restarting services, running database migrations via Prisma, or entering container shells without manual SSH configuration.
  • Infrastructure Health Checks: Verify database connectivity and resource utilization across the entire stack to ensure the fyzz.dev application remains performant and stable.
namefizz-production
descriptionEnables Copilot to SSH into the Fizz EC2 instance and manage Docker containers for the fyzz.dev production app.

Fizz Production Management Skill

This skill enables you to manage the Fizz lead generation application running on AWS EC2.

Architecture Overview

Fizz is a Next.js application deployed on EC2 with the following components:

  • fizz-app: Main Next.js web application (port 3000)
  • fizz-postgres: PostgreSQL 16 database
  • fizz-redis: Redis for rate limiting and caching
  • fizz-caddy: Caddy reverse proxy with automatic HTTPS
  • Workers: Background job processors
    • fizz-worker-discovery: Lead discovery
    • fizz-worker-screenshots: Website screenshots
    • fizz-worker-lighthouse: Performance analysis
    • fizz-worker-vision: AI vision analysis
    • fizz-worker-sections: Section extraction
    • fizz-worker-email: Email generation
    • fizz-worker-followup: Follow-up email handling

Using the FizzAws PowerShell Module

First, import the module:

Import-Module .\FizzAws.psm1

Common Operations

Connect to the server:

Connect-FizzServer

View container status:

Get-FizzContainers
Get-FizzHealth

View logs:

Get-FizzLogs -Container app -Tail 100
Get-FizzLogs -Container worker-discovery -Follow
Watch-FizzLogs  # All containers

Debug errors:

Get-FizzErrors
Get-FizzStats

Restart containers:

Restart-FizzContainer -Container app
Invoke-FizzCompose -Action restart

Enter container shell:

Enter-FizzContainer -Container app
Enter-FizzContainer -Container postgres -Shell /bin/bash

Run commands in containers:

Invoke-FizzDocker -Container app -Command "npx prisma studio"
Invoke-FizzDocker -Container postgres -Command "psql -U fizz -d fizz"

Infrastructure Details

  • Domain: fyzz.dev (Route53 managed)
  • EC2: Ubuntu 22.04, t3.small
  • RDS: PostgreSQL on db.t4g.micro
  • Region: us-east-1
  • SSH User: ubuntu

Debugging Checklist

When investigating production issues:

  1. Check container health: Get-FizzHealth
  2. Look for errors: Get-FizzErrors
  3. Check specific container logs: Get-FizzLogs -Container <name>
  4. Verify database connectivity: Test-FizzDatabase
  5. Check resource usage: Get-FizzStats
  6. Review recent deployments in the fizz repository

Environment Variables

The app uses these key environment variables:

  • DATABASE_URL: PostgreSQL connection string
  • REDIS_URL: Redis connection string
  • ANTHROPIC_API_KEY: For AI features
  • SERPAPI_API_KEY: For search functionality
  • PAGESPEED_API_KEY: For Lighthouse analysis
  • AUTH_SECRET: Authentication secret
  • SMARTLEAD_API_KEY: For email campaigns