langfuse-multi-env-setup
Configure Langfuse across development, staging, and production environments. Use when setting up multi-environment deployments, configuring per-environment keys, or implementing environment-specific Langfuse configurations. Trigger with phrases like "langfuse environments", "langfuse staging", "langfuse dev prod", "langfuse environment setup", "langfuse config by env". '
Profile →npx skills add jeremylongshore/claude-code-plugins-plus-skills --skill langfuse-multi-env-setup --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Langfuse Multi-Environment Setup ## Overview Configure Langfuse across dev/staging/production with isolated API keys, environment-specific SDK settings, secret management, and CI/CD integration to prevent cross-environment data leakage. ## Prerequisites - Separate Langfuse API key pairs per environment (or separate projects) - Secret management solution (env vars, Vault, AWS/GCP secrets) - CI/CD pipeline with environment-aware deployment ## Environment Strategy | Environment | API Key Source | Langfuse Project | Settings | |-------------|---------------|-----------------|----------| | Development | `.env.local` | Dev project | Debug on, flush immediately, 100% sampling | | Staging | CI/CD secrets | Staging project | Prod-like settings, 50% sampling | | Production | Secret manager | Prod project | Optimized batching, 10% sampling | ## Instructions ### Step 1: Environment-Specific Configuration ```typescript // src/config/langfuse.ts import { LangfuseSpanProcessor } from "@langfuse/otel"; import { NodeSDK } from "@opentelemetry/sdk-node"; import { LangfuseClient } from "@langfuse/client"; type Env = "development" | "staging" | "production"; interface LangfuseEnvConfig { exportInter
- Overview
- Prerequisites
- Environment Strategy
- Instructions
- Step 1: Environment-Specific Configuration
- Step 2: Environment Variable Files
- Step 3: Secret Management
- Step 4: CI/CD Integration
- Step 5: Startup Validation with Zod
- Cross-Environment Safety
- Error Handling
- Resources
Keys injected via CI secrets Keys injected via secret manager set -euo pipefail GitHub Actions: Add per-environment secrets Settings > Environments > staging > Secrets Settings > Environments > production > Secrets AWS Secrets Manager aws secretsmanager create-secret \ GCP Secret Manager echo -n "pk-lf-prod-..." | gcloud secrets create langfuse-public-key-prod --data-file=-
What does the langfuse-multi-env-setup skill do?
Configure Langfuse across development, staging, and production environments. Use when setting up multi-environment deployments, configuring per-environment keys, or implementing environment-specific Langfuse configurations. Trigger with phrases like "langfuse environments", "langfuse staging", "langfuse dev prod", "langfuse environment setup", "langfuse config by env". '
How do I install it?
Run `npx skills add jeremylongshore/claude-code-plugins-plus-skills --skill langfuse-multi-env-setup --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From jeremylongshore/claude-code-plugins-plus-skills, a repository with 2,630 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.