langchain-multi-env-setup
Configure LangChain multi-environment setup for dev/staging/prod. Use when managing multiple environments, configuring environment-specific settings, or implementing environment promotion workflows. Trigger with phrases like "langchain environments", "langchain staging", "langchain dev prod", "environment configuration", "langchain env setup".
Install
mkdir -p .claude/skills/langchain-multi-env-setup && curl -L -o skill.zip "https://mcp.directory/api/skills/download/7437" && unzip -o skill.zip -d .claude/skills/langchain-multi-env-setup && rm skill.zipInstalls to .claude/skills/langchain-multi-env-setup
About this skill
LangChain Multi-Environment Setup
Overview
Configure LangChain across development, staging, and production with separate API keys, environment-specific model settings, LangSmith project isolation, and validated configuration.
Environment Strategy
| Environment | API Key Source | Model | LangSmith Project | Cache |
|---|---|---|---|---|
| Development | .env.local | gpt-4o-mini | dev-{user} | Off |
| Staging | CI secrets | gpt-4o-mini | staging | Redis |
| Production | Secret Manager | gpt-4o | production | Redis |
Step 1: Configuration with Zod Validation
// config/langchain.ts
import { z } from "zod";
import "dotenv/config";
const EnvironmentSchema = z.enum(["development", "staging", "production"]);
const ConfigSchema = z.object({
environment: EnvironmentSchema,
openaiApiKey: z.string().min(1, "OPENAI_API_KEY is required"),
model: z.string().default("gpt-4o-mini"),
temperature: z.number().min(0).max(2).default(0),
maxRetries: z.number().default(3),
timeout: z.number().default(30000),
langsmith: z.object({
enabled: z.boolean(),
apiKey: z.string().optional(),
project: z.string(),
}),
cache: z.object({
enabled: z.boolean(),
ttlSeconds: z.number().default(300),
}),
});
export type LangChainConfig = z.infer<typeof ConfigSchema>;
function detectEnvironment(): z.infer<typeof EnvironmentSchema> {
const env = process.env.NODE_ENV ?? "development";
if (env === "production") return "production";
if (env === "staging" || process.env.VERCEL_ENV === "preview") return "staging";
return "development";
}
const ENV_CONFIGS: Record<string, Partial<z.infer<typeof ConfigSchema>>> = {
development: {
model: "gpt-4o-mini",
temperature: 0,
timeout: 60000,
langsmith: { enabled: true, project: `dev-${process.env.USER ?? "local"}` },
cache: { enabled: false, ttlSeconds: 60 },
},
staging: {
model: "gpt-4o-mini",
temperature: 0,
langsmith: { enabled: true, project: "staging" },
cache: { enabled: true, ttlSeconds: 300 },
},
production: {
model: "gpt-4o",
temperature: 0,
maxRetries: 5,
timeout: 60000,
langsmith: { enabled: true, project: "production" },
cache: { enabled: true, ttlSeconds: 600 },
},
};
export function loadConfig(): LangChainConfig {
const env = detectEnvironment();
const envConfig = ENV_CONFIGS[env];
const raw = {
environment: env,
openaiApiKey: process.env.OPENAI_API_KEY,
...envConfig,
langsmith: {
...envConfig?.langsmith,
apiKey: process.env.LANGSMITH_API_KEY,
enabled: process.env.LANGSMITH_TRACING === "true",
},
};
const config = ConfigSchema.parse(raw);
console.log(`[config] Environment: ${config.environment}, Model: ${config.model}`);
return config;
}
Step 2: Environment Files
# .env.example (commit this)
OPENAI_API_KEY=
ANTHROPIC_API_KEY=
LANGSMITH_API_KEY=
LANGSMITH_TRACING=true
NODE_ENV=development
# .env.local (git-ignored, for local dev)
OPENAI_API_KEY=sk-dev-...
LANGSMITH_API_KEY=lsv2_pt_dev_...
LANGSMITH_TRACING=true
NODE_ENV=development
# .gitignore
.env
.env.local
.env.*.local
Step 3: Secret Management
# GitHub Actions — use environments
# Settings > Environments > staging > Secrets
# OPENAI_API_KEY, LANGSMITH_API_KEY
# GCP Secret Manager
echo -n "sk-prod-..." | gcloud secrets create openai-api-key-prod --data-file=-
echo -n "lsv2_..." | gcloud secrets create langsmith-api-key-prod --data-file=-
# AWS Secrets Manager
aws secretsmanager create-secret \
--name langchain/production/openai-key \
--secret-string "sk-prod-..."
Step 4: CI/CD with Environment Isolation
# .github/workflows/deploy.yml
jobs:
deploy-staging:
environment: staging
env:
NODE_ENV: staging
OPENAI_API_KEY: ${{ secrets.OPENAI_API_KEY }}
LANGSMITH_API_KEY: ${{ secrets.LANGSMITH_API_KEY }}
LANGSMITH_TRACING: "true"
steps:
- uses: actions/checkout@v4
- run: npm ci && npm run build
- run: npm test
- run: gcloud run deploy langchain-api-staging --source .
deploy-production:
environment: production
needs: deploy-staging
env:
NODE_ENV: production
OPENAI_API_KEY: ${{ secrets.OPENAI_API_KEY }}
LANGSMITH_API_KEY: ${{ secrets.LANGSMITH_API_KEY }}
LANGSMITH_TRACING: "true"
steps:
- uses: actions/checkout@v4
- run: npm ci && npm run build
- run: npm test
- run: gcloud run deploy langchain-api --source .
Step 5: Use Config in Application
// src/index.ts
import { loadConfig } from "./config/langchain";
import { createModel } from "./infra/llm/factory";
const config = loadConfig();
// Model automatically configured for environment
const model = createModel({
provider: "openai",
model: config.model,
temperature: config.temperature,
maxRetries: config.maxRetries,
timeout: config.timeout,
});
// LangSmith tracing via env vars (automatic)
if (config.langsmith.enabled) {
process.env.LANGSMITH_TRACING = "true";
process.env.LANGSMITH_API_KEY = config.langsmith.apiKey ?? "";
process.env.LANGSMITH_PROJECT = config.langsmith.project;
}
Startup Validation
// Fail fast on missing config
try {
const config = loadConfig();
console.log(`[startup] Config validated: ${config.environment}`);
} catch (error) {
console.error("[startup] Invalid configuration:", error);
process.exit(1);
}
Error Handling
| Issue | Cause | Fix |
|---|---|---|
| Wrong environment detected | NODE_ENV not set | Set in deployment config |
| Secret not found | Wrong secret path | Verify in cloud console |
| Cross-env data leak | Shared API key | Use separate keys per environment |
| Config validation fail | Missing env var | Check .env.example for required vars |
Resources
Next Steps
For deployment, see langchain-deploy-integration.
More by jeremylongshore
View all skills by jeremylongshore →You might also like
flutter-development
aj-geddes
Build beautiful cross-platform mobile apps with Flutter and Dart. Covers widgets, state management with Provider/BLoC, navigation, API integration, and material design.
drawio-diagrams-enhanced
jgtolentino
Create professional draw.io (diagrams.net) diagrams in XML format (.drawio files) with integrated PMP/PMBOK methodologies, extensive visual asset libraries, and industry-standard professional templates. Use this skill when users ask to create flowcharts, swimlane diagrams, cross-functional flowcharts, org charts, network diagrams, UML diagrams, BPMN, project management diagrams (WBS, Gantt, PERT, RACI), risk matrices, stakeholder maps, or any other visual diagram in draw.io format. This skill includes access to custom shape libraries for icons, clipart, and professional symbols.
ui-ux-pro-max
nextlevelbuilder
"UI/UX design intelligence. 50 styles, 21 palettes, 50 font pairings, 20 charts, 8 stacks (React, Next.js, Vue, Svelte, SwiftUI, React Native, Flutter, Tailwind). Actions: plan, build, create, design, implement, review, fix, improve, optimize, enhance, refactor, check UI/UX code. Projects: website, landing page, dashboard, admin panel, e-commerce, SaaS, portfolio, blog, mobile app, .html, .tsx, .vue, .svelte. Elements: button, modal, navbar, sidebar, card, table, form, chart. Styles: glassmorphism, claymorphism, minimalism, brutalism, neumorphism, bento grid, dark mode, responsive, skeuomorphism, flat design. Topics: color palette, accessibility, animation, layout, typography, font pairing, spacing, hover, shadow, gradient."
godot
bfollington
This skill should be used when working on Godot Engine projects. It provides specialized knowledge of Godot's file formats (.gd, .tscn, .tres), architecture patterns (component-based, signal-driven, resource-based), common pitfalls, validation tools, code templates, and CLI workflows. The `godot` command is available for running the game, validating scripts, importing resources, and exporting builds. Use this skill for tasks involving Godot game development, debugging scene/resource files, implementing game systems, or creating new Godot components.
nano-banana-pro
garg-aayush
Generate and edit images using Google's Nano Banana Pro (Gemini 3 Pro Image) API. Use when the user asks to generate, create, edit, modify, change, alter, or update images. Also use when user references an existing image file and asks to modify it in any way (e.g., "modify this image", "change the background", "replace X with Y"). Supports both text-to-image generation and image-to-image editing with configurable resolution (1K default, 2K, or 4K for high resolution). DO NOT read the image file first - use this skill directly with the --input-image parameter.
fastapi-templates
wshobson
Create production-ready FastAPI projects with async patterns, dependency injection, and comprehensive error handling. Use when building new FastAPI applications or setting up backend API projects.
Related MCP Servers
Browse all serversAccess Cloudflare documentation fast via a Cloudflare Worker using an indexed Vectorize DB. Ideal for Cloudflare API doc
MCP Installer simplifies dynamic installation and configuration of additional MCP servers. Get started easily with MCP I
Easily integrate and debug Sentry APIs with sentry-mcp, a flexible MCP middleware for cloud and self-hosted setups.
Seamlessly connect Hugging Face Spaces with your AI assistants for instant access to powerful AI models—no manual setup
Manage Alibaba Cloud ECS, monitor metrics, and configure VPC networks effortlessly using natural language commands with
Replicate Flux is an OpenAPI image generator using Replicate's Flux model, enabling image creation via API and TypeScrip
Stay ahead of the MCP ecosystem
Get weekly updates on new skills and servers.