micsapp Lindy AI Multi-Environment Setup
Overview
Configure Lindy AI across development, staging, and production environments with isolated API keys, environment-specific settings, and proper secret management. Each environment gets its own credentials and configuration to prevent cross-environment data leakage.
Prerequisites
- Separate Lindy AI API keys per environment
- Secret management solution (environment variables, Vault, or cloud secrets)
- CI/CD pipeline with environment-aware deployment
- Application with environment detection logic
Environment Strategy
| Environment | Purpose | API Key Source | Settings |
|---|---|---|---|
| Development | Local development | .env.local |
Debug enabled, relaxed limits |
| Staging | Pre-production testing | CI/CD secrets | Production-like settings |
| Production | Live traffic | Secret manager | Optimized, hardened |
Instructions
Step 1: Configuration Structure
Step 2: Base Configuration
Step 3: Environment-Specific Configs
Step 4: Environment Resolver
Step 5: Secret Management
For detailed implementation code and configurations, load the reference guide:
Read(${CLAUDE_SKILL_DIR}/references/implementation-guide.md)
Error Handling
| Issue | Cause | Solution |
|---|---|---|
| Wrong environment | Missing NODE_ENV | Set environment variable in deployment |
| Secret not found | Wrong secret path | Verify secret manager configuration |
| Cross-env data leak | Shared API key | Use separate keys per environment |
| Config validation fail | Missing field | Add startup validation with Zod schema |
Examples
Quick Environment Check
Startup Validation
Resources
Next Steps
For deployment, see lindy-deploy-integration.
Output
- Configuration files or code changes applied to the project
- Validation report confirming correct implementation
- Summary of changes made and their rationale
See deployment implementation details for output format specifications.