flyio-deploy-integration

Deploy Fly.io integrations to Vercel, Fly.io, and Cloud Run platforms. Use when deploying Fly.io-powered applications to production, configuring platform-specific secrets, or setting up deployment pipelines. Trigger with phrases like "deploy flyio", "flyio Vercel", "flyio production deploy", "flyio Cloud Run", "flyio Fly.io".

claude-code
6 Tools
flyio-pack Plugin
saas packs Category

Allowed Tools

ReadWriteEditBash(vercel:*)Bash(fly:*)Bash(gcloud:*)

Provided by Plugin

flyio-pack

Claude Code skill pack for Fly.io (18 skills)

saas packs v1.0.0
View Plugin

Installation

This skill is included in the flyio-pack plugin:

/plugin install flyio-pack@claude-code-plugins-plus

Click to copy

Instructions

Fly.io Deploy Integration

Overview

Deploy Fly.io-powered applications to popular platforms with proper secrets management.

Prerequisites

  • Fly.io API keys for production environment
  • Platform CLI installed (vercel, fly, or gcloud)
  • Application code ready for deployment
  • Environment variables documented

Vercel Deployment

Environment Setup


# Add Fly.io secrets to Vercel
vercel secrets add flyio_api_key sk_live_***
vercel secrets add flyio_webhook_secret whsec_***

# Link to project
vercel link

# Deploy preview
vercel

# Deploy production
vercel --prod

vercel.json Configuration


{
  "env": {
    "FLYIO_API_KEY": "@flyio_api_key"
  },
  "functions": {
    "api/**/*.ts": {
      "maxDuration": 30
    }
  }
}

Fly.io Deployment

fly.toml


app = "my-flyio-app"
primary_region = "iad"

[env]
  NODE_ENV = "production"

[http_service]
  internal_port = 3000
  force_https = true
  auto_stop_machines = true
  auto_start_machines = true

Secrets


# Set Fly.io secrets
fly secrets set FLYIO_API_KEY=sk_live_***
fly secrets set FLYIO_WEBHOOK_SECRET=whsec_***

# Deploy
fly deploy

Google Cloud Run

Dockerfile


FROM node:20-slim
WORKDIR /app
COPY package*.json ./
RUN npm ci --only=production
COPY . .
CMD ["npm", "start"]

Deploy Script


#!/bin/bash
# deploy-cloud-run.sh

PROJECT_ID="${GOOGLE_CLOUD_PROJECT}"
SERVICE_NAME="flyio-service"
REGION="us-central1"

# Build and push image
gcloud builds submit --tag gcr.io/$PROJECT_ID/$SERVICE_NAME

# Deploy to Cloud Run
gcloud run deploy $SERVICE_NAME \
  --image gcr.io/$PROJECT_ID/$SERVICE_NAME \
  --region $REGION \
  --platform managed \
  --allow-unauthenticated \
  --set-secrets=FLYIO_API_KEY=flyio-api-key:latest

Environment Configuration Pattern


// config/flyio.ts
interface Fly.ioConfig {
  apiKey: string;
  environment: 'development' | 'staging' | 'production';
  webhookSecret?: string;
}

export function getFly.ioConfig(): Fly.ioConfig {
  const env = process.env.NODE_ENV || 'development';

  return {
    apiKey: process.env.FLYIO_API_KEY!,
    environment: env as Fly.ioConfig['environment'],
    webhookSecret: process.env.FLYIO_WEBHOOK_SECRET,
  };
}

Health Check Endpoint


// api/health.ts
export async function GET() {
  const flyioStatus = await checkFly.ioConnection();

  return Response.json({
    status: flyioStatus ? 'healthy' : 'degraded',
    services: {
      flyio: flyioStatus,
    },
    timestamp: new Date().toISOString(),
  });
}

Instructions

Step 1: Choose Deployment Platform

Select the platform that best fits your infrastructure needs and follow the platform-specific guide below.

Step 2: Configure Secrets

Store Fly.io API keys securely using the platform's secrets management.

Step 3: Deploy Application

Use the platform CLI to deploy your application with Fly.io integration.

Step 4: Verify Health

Test the health check endpoint to confirm Fly.io connectivity.

Output

  • Application deployed to production
  • Fly.io secrets securely configured
  • Health check endpoint functional
  • Environment-specific configuration in place

Error Handling

Issue Cause Solution
Secret not found Missing configuration Add secret via platform CLI
Deploy timeout Large build Increase build timeout
Health check fails Wrong API key Verify environment variable
Cold start issues No warm-up Configure minimum instances

Examples

Quick Deploy Script


#!/bin/bash
# Platform-agnostic deploy helper
case "$1" in
  vercel)
    vercel secrets add flyio_api_key "$FLYIO_API_KEY"
    vercel --prod
    ;;
  fly)
    fly secrets set FLYIO_API_KEY="$FLYIO_API_KEY"
    fly deploy
    ;;
esac

Resources

Next Steps

For webhook handling, see flyio-webhooks-events.

Ready to use flyio-pack?