firecrawl-multi-env-setup

# Firecrawl Multi-Environment Setup ## Overview Firecrawl's credit-based pricing makes environment separation critical. Development should use self-hosted Firecrawl or strict limits to avoid burning production credits during testing. This skill covers per-environment config, self-hosted Docker for dev, and credit budget enforcement. ## Environment Strategy | Environment | API Source | Crawl Limit | Concurrency | Credits | |-------------|-----------|-------------|-------------|---------| | Development | Self-hosted Docker | 10 pages | 1 | Zero (local) | | Staging | Cloud API (test key) | 50 pages | 2 | Limited | | Production | Cloud API (prod key) | Per-task | Full plan | Monitored | ## Instructions ### Step 1: Environment-Aware Configuration ```typescript // config/firecrawl.ts import FirecrawlApp from "@mendable/firecrawl-js"; type Env = "development" | "staging" | "production"; interface FirecrawlConfig { apiKey: string; apiUrl?: string; maxPagesPerCrawl: number; maxDepth: number; concurrency: number; waitFor: number; } const configs: Record<Env, FirecrawlConfig> = { development: { apiKey: process.env.FIRECRAWL_API_KEY_DEV || "fc-localdev", apiUrl: process.env.FIRECRAWL_API_URL_DEV || "http://localhost:3002", maxPagesPerCrawl: 10, maxDepth: 2, concurrency: 1, waitFor: 2000, }, staging: { apiKey: process.env.FIRECRAWL_API_KEY_STAGING!, maxPagesPerCrawl: 50, maxDepth: 3, concurrency: 2, waitFor: 3000, }, ...