groq-deploy-integration
Deploy Groq integrations to Vercel, Fly.io, and Cloud Run platforms. Use when deploying Groq-powered applications to production, configuring platform-specific secrets, or setting up deployment pipelines. Trigger with phrases like "deploy groq", "groq Vercel", "groq production deploy", "groq Cloud Run", "groq Fly.io".
- License 许可
- MIT
- 最近更新
- 2026-11-15
- Stars
- ★ 2.0k
- Forks
- 233
01 前言 Front Matter
- name
- groq-deploy-integration
- author
- Jeremy Longshore <jeremy@intentsolutions.io>
- license
- MIT
- version
- 1.0.0
- description
- Deploy Groq integrations to Vercel, Fly.io, and Cloud Run platforms. Use when deploying Groq-powered applications to production, configuring platform-specific secrets, or setting up deployment pipelines. Trigger with phrases like "deploy groq", "groq Vercel", "groq production deploy", "groq Cloud Run", "groq Fly.io".
- allowed-tools
- Read, Write, Edit, Bash(vercel:*), Bash(fly:*), Bash(gcloud:*)
03 SKILL.md 正文
Groq Deploy Integration
Overview
Deploy Groq-powered applications to popular platforms with proper secrets management.
Prerequisites
- Groq 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 Groq secrets to Vercel
vercel secrets add groq_api_key sk_live_***
vercel secrets add groq_webhook_secret whsec_***
# Link to project
vercel link
# Deploy preview
vercel
# Deploy production
vercel --prod
vercel.json Configuration
{
"env": {
"GROQ_API_KEY": "@groq_api_key"
},
"functions": {
"api/**/*.ts": {
"maxDuration": 30
}
}
}
Fly.io Deployment
fly.toml
app = "my-groq-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 Groq secrets
fly secrets set GROQ_API_KEY=sk_live_***
fly secrets set GROQ_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="groq-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=GROQ_API_KEY=groq-api-key:latest
Environment Configuration Pattern
// config/groq.ts
interface GroqConfig {
apiKey: string;
environment: 'development' | 'staging' | 'production';
webhookSecret?: string;
}
export function getGroqConfig(): GroqConfig {
const env = process.env.NODE_ENV || 'development';
return {
apiKey: process.env.GROQ_API_KEY!,
environment: env as GroqConfig['environment'],
webhookSecret: process.env.GROQ_WEBHOOK_SECRET,
};
}
Health Check Endpoint
// api/health.ts
export async function GET() {
const groqStatus = await checkGroqConnection();
return Response.json({
status: groqStatus ? 'healthy' : 'degraded',
services: {
groq: groqStatus,
},
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 Groq API keys securely using the platform's secrets management.
Step 3: Deploy Application
Use the platform CLI to deploy your application with Groq integration.
Step 4: Verify Health
Test the health check endpoint to confirm Groq connectivity.
Output
- Application deployed to production
- Groq 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 groq_api_key "$GROQ_API_KEY"
vercel --prod
;;
fly)
fly secrets set GROQ_API_KEY="$GROQ_API_KEY"
fly deploy
;;
esac
Resources
Next Steps
For webhook handling, see groq-webhooks-events.
04 同仓库更多 Skills
theme-factory
Toolkit for styling artifacts with a theme. These artifacts can be slides, docs, reportings, HTML landing pages, etc. There are 10 pre-set themes with colors/fonts that you can apply to any artifact that has been creating, or can generate a new theme on-the-fly.
web-artifacts-builder
Suite of tools for creating elaborate, multi-component claude.ai HTML artifacts using modern frontend web technologies (React, Tailwind CSS, shadcn/ui). Use for complex artifacts requiring state management, routing, or shadcn/ui components - not for simple single-file HTML/JSX artifacts.
webapp-testing
Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.
neuropixels-analysis
Neuropixels neural recording analysis. Load SpikeGLX/OpenEphys data, preprocess, motion correction, Kilosort4 spike sorting, quality metrics, Allen/IBL curation, AI-assisted visual analysis, for Neuropixels 1.0/2.0 extracellular electrophysiology. Use when working with neural recordings, spike sorting, extracellular electrophysiology, or when the user mentions Neuropixels, SpikeGLX, Open Ephys, Kilosort, quality metrics, or unit curation.
skill-creator
Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Claude's capabilities with specialized knowledge, workflows, or tool integrations.
notebooklm
Use this skill to query your Google NotebookLM notebooks directly from Claude Code for source-grounded, citation-backed answers from Gemini. Browser automation, library management, persistent auth. Drastically reduced hallucinations through document-only responses.