Deploy Ideogram integrations to Vercel, Fly.io, and Cloud Run platforms. Use when deploying Ideogram-powered applications to production, configuring platform-specific secrets, or setting up deployment pipelines. Trigger with phrases like "deploy ideogram", "ideogram Vercel", "ideogram production deploy", "ideogram Cloud Run", "ideogram Fly.io".
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill ideogram-deploy-integration93
Does it follow best practices?
Validation for skill structure
Deploy Ideogram-powered applications to popular platforms with proper secrets management.
# Add Ideogram secrets to Vercel
vercel secrets add ideogram_api_key sk_live_***
vercel secrets add ideogram_webhook_secret whsec_***
# Link to project
vercel link
# Deploy preview
vercel
# Deploy production
vercel --prod{
"env": {
"IDEOGRAM_API_KEY": "@ideogram_api_key"
},
"functions": {
"api/**/*.ts": {
"maxDuration": 30
}
}
}app = "my-ideogram-app"
primary_region = "iad"
[env]
NODE_ENV = "production"
[http_service]
internal_port = 3000
force_https = true
auto_stop_machines = true
auto_start_machines = true# Set Ideogram secrets
fly secrets set IDEOGRAM_API_KEY=sk_live_***
fly secrets set IDEOGRAM_WEBHOOK_SECRET=whsec_***
# Deploy
fly deployFROM node:20-slim
WORKDIR /app
COPY package*.json ./
RUN npm ci --only=production
COPY . .
CMD ["npm", "start"]#!/bin/bash
# deploy-cloud-run.sh
PROJECT_ID="${GOOGLE_CLOUD_PROJECT}"
SERVICE_NAME="ideogram-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=IDEOGRAM_API_KEY=ideogram-api-key:latest// config/ideogram.ts
interface IdeogramConfig {
apiKey: string;
environment: 'development' | 'staging' | 'production';
webhookSecret?: string;
}
export function getIdeogramConfig(): IdeogramConfig {
const env = process.env.NODE_ENV || 'development';
return {
apiKey: process.env.IDEOGRAM_API_KEY!,
environment: env as IdeogramConfig['environment'],
webhookSecret: process.env.IDEOGRAM_WEBHOOK_SECRET,
};
}// api/health.ts
export async function GET() {
const ideogramStatus = await checkIdeogramConnection();
return Response.json({
status: ideogramStatus ? 'healthy' : 'degraded',
services: {
ideogram: ideogramStatus,
},
timestamp: new Date().toISOString(),
});
}Select the platform that best fits your infrastructure needs and follow the platform-specific guide below.
Store Ideogram API keys securely using the platform's secrets management.
Use the platform CLI to deploy your application with Ideogram integration.
Test the health check endpoint to confirm Ideogram connectivity.
| 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 |
#!/bin/bash
# Platform-agnostic deploy helper
case "$1" in
vercel)
vercel secrets add ideogram_api_key "$IDEOGRAM_API_KEY"
vercel --prod
;;
fly)
fly secrets set IDEOGRAM_API_KEY="$IDEOGRAM_API_KEY"
fly deploy
;;
esacFor webhook handling, see ideogram-webhooks-events.
9659b78
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.