Browse / Deployment Devops / Deploy Shot Client Next

Deploy Shot Client Next

Deploys the shot-client-next Next.js frontend to Fly.io with automated build verification and environment configuration.

SkillDeployment DevopsReleaseCliConfig

The source repository doesn't declare a license. Check its terms before reusing the code.

Key features

  • Environment variable and secret management guidance
  • Automated Fly.io deployment and real-time log monitoring
  • Post-release health checks for WebSocket and API connectivity
  • Local build verification and TypeScript error checking
  • Standardized rollback and troubleshooting procedures

Use cases

  • Deploying bug fixes and verifying critical application flows
  • Updating production environment variables and API URLs
  • Releasing UI updates and feature enhancements to production

FAQ

How does this skill improve my workflow?

It reduces deployment risk by enforcing a pre-deployment checklist, ensuring the code builds locally without TypeScript errors before pushing to production, and providing standardized procedures for monitoring and health checks.

When should I use this skill?

Use this skill whenever you need to release UI updates, update production environment variables, or push new versions of the frontend to Fly.io. It is designed for both minor patches and major production releases.

Does this skill handle WebSocket and API configurations?

Yes, it includes specific steps to verify production environment variables like NEXT_PUBLIC_API_URL and NEXT_PUBLIC_WS_URL, ensuring the frontend correctly connects to the backend services after deployment.

What does the Deploy Shot Client Next skill do?

This skill automates the deployment of the shot-client-next Next.js application to Fly.io. It orchestrates the entire process including local build verification, Git status checks, Fly.io deployment commands, and real-time log monitoring.

What capabilities does it provide for troubleshooting?

The skill includes specific instructions for monitoring deployment logs with 'fly logs', verifying environment variables via 'fly secrets', and executing rapid rollbacks if a deployment fails to meet health check standards.