smithery/marcusshepp

fizz-production

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

Installation

$ npx skills add smithery/marcusshepp --skill fizz-production

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from smithery/marcusshepp.

npx skills add smithery/marcusshepp

Browse all from smithery/marcusshepp

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 2,831 B
  • docs SUMMARY.md 134 B

History

  1. First recorded snapshot · 0 installs

SKILL.md

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
  • ANTHROPICAPIKEY: For AI features
  • SERPAPIAPIKEY: For search functionality
  • PAGESPEEDAPIKEY: For Lighthouse analysis
  • AUTH_SECRET: Authentication secret
  • SMARTLEADAPIKEY: For email campaigns