juicebox-multi-env-setup

# Juicebox Multi-Environment Setup ## Overview Juicebox AI analysis requires environment separation to enforce workspace isolation, control data access, and prevent accidental exports of sensitive datasets. Development works with sample datasets and strict result limits for fast iteration, staging connects to full production data but disables export functionality, and production enables all features with full export capabilities. Each environment uses isolated workspaces so analysis experiments in dev never affect production workspace state or user-facing reports. ## Environment Configuration ```typescript const juiceboxConfig = (env: string) => ({ development: { apiKey: process.env.JB_KEY_DEV!, baseUrl: "https://api.dev.juicebox.work/v1", workspaceId: process.env.JB_WORKSPACE_DEV!, resultLimit: 5, exportEnabled: false, }, staging: { apiKey: process.env.JB_KEY_STG!, baseUrl: "https://api.staging.juicebox.work/v1", workspaceId: process.env.JB_WORKSPACE_STG!, resultLimit: 20, exportEnabled: false, }, production: { apiKey: process.env.JB_KEY_PROD!, baseUrl: "https://api.juicebox.work/v1", workspaceId: process.env.JB_WORKSPACE_PROD!, resultLimit: 50, exportEnabled: true, }, }[env]); ``` ## Environment Files ```bash # Per-env files: .env.development, .env.staging, .env.production JB_KEY_{DEV|STG|PROD}=<api-key> JB_WORKSPACE_{DEV|STG|PROD}=<workspace-id> JB_BASE_URL=https://api.{dev.|staging.|""}juicebox.work/v1 JB_EXPORT_ENABLED={false|fal...