Writing Skills
writing-skills
效率与协作技能,来自 obra/superpowers,查看原文获取完整用途和操作说明。
perplexity-deploy-integration【部署与运维】Deploy Perplexity integrations to Vercel, Fly.io, and Cloud Run platforms. Use when deploying Perplexity-powered applications to production, configuring platform-specific secrets, or setting up deployment pipelines. Trigger with phrases like "deploy perplexity", "perplexity Vercel", "perplexity production deploy", "perplexity Cloud Run", "perplexity …
独立 GitHub 快照 · 自动分类 · 以原作者文档为准
Deploy Perplexity-powered applications to popular platforms with proper secrets management.
# Add Perplexity secrets to Vercel
vercel secrets add perplexity_api_key sk_live_***
vercel secrets add perplexity_webhook_secret whsec_***
# Link to project
vercel link
# Deploy preview
vercel
# Deploy production
vercel --prod
{
"env": {
"PERPLEXITY_API_KEY": "@perplexity_api_key"
},
"functions": {
"api/**/*.ts": {
"maxDuration": 30
}
}
}
app = "my-perplexity-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 Perplexity secrets
fly secrets set PERPLEXITY_API_KEY=sk_live_***
fly secrets set PERPLEXITY_WEBHOOK_SECRET=whsec_***
# Deploy
fly deploy
FROM 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="perplexity-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=PERPLEXITY_API_KEY=perplexity-api-key:latest
// config/perplexity.ts
interface PerplexityConfig {
apiKey: string;
environment: 'development' | 'staging' | 'production';
webhookSecret?: string;
}
export function getPerplexityConfig(): PerplexityConfig {
const env = process.env.NODE_ENV || 'development';
return {
apiKey: process.env.PERPLEXITY_API_KEY!,
environment: env as PerplexityConfig['environment'],
webhookSecret: process.env.PERPLEXITY_WEBHOOK_SECRET,
};
}
// api/health.ts
export async function GET() {
const perplexityStatus = await checkPerplexityConnection();
return Response.json({
status: perplexityStatus ? 'healthy' : 'degraded',
services: {
perplexity: perplexityStatus,
},
timestamp: new Date().toISOString(),
});
}
Select the platform that best fits your infrastructure needs and follow the platform-specific guide below.
Store Perplexity API keys securely using the platform's secrets management.
Use the platform CLI to deploy your application with Perplexity integration.
Test the health check endpoint to confirm Perplexity 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 perplexity_api_key "$PERPLEXITY_API_KEY"
vercel --prod
;;
fly)
fly secrets set PERPLEXITY_API_KEY="$PERPLEXITY_API_KEY"
fly deploy
;;
esac
For webhook handling, see perplexity-webhooks-events.