cim_summary/TESTING_CONFIG_SETUP.md

🔧 Testing Environment Configuration Setup

Step-by-step guide to configure your testing environment with Week 8 features

✅ Firebase Configuration (COMPLETED)

Great! You already have your Firebase testing project set up. Here are your credentials:

# Firebase Configuration
FB_PROJECT_ID=cim-summarizer-testing
FB_STORAGE_BUCKET=cim-summarizer-testing.firebasestorage.app
FB_API_KEY=AIzaSyBNf58cnNMbXb6VE3sVEJYJT5CGNQr0Kmg
FB_AUTH_DOMAIN=cim-summarizer-testing.firebaseapp.com

📋 Next Steps Required

Step 1: Create Testing Environment File

Create backend/.env.testing with the following content:

# Node Environment
NODE_ENV=testing

# Firebase Configuration (Testing Project) - ✅ COMPLETED
FB_PROJECT_ID=cim-summarizer-testing
FB_STORAGE_BUCKET=cim-summarizer-testing.firebasestorage.app
FB_API_KEY=AIzaSyBNf58cnNMbXb6VE3sVEJYJT5CGNQr0Kmg
FB_AUTH_DOMAIN=cim-summarizer-testing.firebaseapp.com

# Supabase Configuration (Testing Instance) - ⚠️ NEEDS SETUP
SUPABASE_URL=https://your-testing-project.supabase.co
SUPABASE_ANON_KEY=your-testing-anon-key
SUPABASE_SERVICE_KEY=your-testing-service-key

# Google Cloud Configuration (Testing Project) - ⚠️ NEEDS SETUP
GCLOUD_PROJECT_ID=cim-summarizer-testing
DOCUMENT_AI_LOCATION=us
DOCUMENT_AI_PROCESSOR_ID=your-testing-processor-id
GCS_BUCKET_NAME=cim-processor-testing-uploads
DOCUMENT_AI_OUTPUT_BUCKET_NAME=cim-processor-testing-processed
GOOGLE_APPLICATION_CREDENTIALS=./serviceAccountKey-testing.json

# LLM Configuration (Same as production but with cost limits) - ⚠️ NEEDS SETUP
LLM_PROVIDER=anthropic
ANTHROPIC_API_KEY=your-anthropic-key
LLM_MAX_COST_PER_DOCUMENT=1.00
LLM_ENABLE_COST_OPTIMIZATION=true
LLM_USE_FAST_MODEL_FOR_SIMPLE_TASKS=true

# Email Configuration (Testing) - ⚠️ NEEDS SETUP
EMAIL_HOST=smtp.gmail.com
EMAIL_PORT=587
EMAIL_USER=your-testing-email@gmail.com
EMAIL_PASS=your-app-password
EMAIL_FROM=noreply@cim-summarizer-testing.com
WEEKLY_EMAIL_RECIPIENT=your-email@company.com

# Vector Database (Testing)
VECTOR_PROVIDER=supabase

# Testing-specific settings
RATE_LIMIT_MAX_REQUESTS=1000
RATE_LIMIT_WINDOW_MS=900000
AGENTIC_RAG_DETAILED_LOGGING=true
AGENTIC_RAG_PERFORMANCE_TRACKING=true
AGENTIC_RAG_ERROR_REPORTING=true

# Week 8 Features Configuration
# Cost Monitoring
COST_MONITORING_ENABLED=true
USER_DAILY_COST_LIMIT=50.00
USER_MONTHLY_COST_LIMIT=500.00
DOCUMENT_COST_LIMIT=10.00
SYSTEM_DAILY_COST_LIMIT=1000.00

# Caching Configuration
CACHE_ENABLED=true
CACHE_TTL_HOURS=168
CACHE_SIMILARITY_THRESHOLD=0.85
CACHE_MAX_SIZE=10000

# Microservice Configuration
MICROSERVICE_ENABLED=true
MICROSERVICE_MAX_CONCURRENT_JOBS=5
MICROSERVICE_HEALTH_CHECK_INTERVAL=30000
MICROSERVICE_QUEUE_PROCESSING_INTERVAL=5000

# Processing Strategy
PROCESSING_STRATEGY=document_ai_agentic_rag
ENABLE_RAG_PROCESSING=true
ENABLE_PROCESSING_COMPARISON=false

# Agentic RAG Configuration
AGENTIC_RAG_ENABLED=true
AGENTIC_RAG_MAX_AGENTS=6
AGENTIC_RAG_PARALLEL_PROCESSING=true
AGENTIC_RAG_VALIDATION_STRICT=true
AGENTIC_RAG_RETRY_ATTEMPTS=3
AGENTIC_RAG_TIMEOUT_PER_AGENT=60000

# Agent-Specific Configuration
AGENT_DOCUMENT_UNDERSTANDING_ENABLED=true
AGENT_FINANCIAL_ANALYSIS_ENABLED=true
AGENT_MARKET_ANALYSIS_ENABLED=true
AGENT_INVESTMENT_THESIS_ENABLED=true
AGENT_SYNTHESIS_ENABLED=true
AGENT_VALIDATION_ENABLED=true

# Quality Control
AGENTIC_RAG_QUALITY_THRESHOLD=0.8
AGENTIC_RAG_COMPLETENESS_THRESHOLD=0.9
AGENTIC_RAG_CONSISTENCY_CHECK=true

# Logging Configuration
LOG_LEVEL=debug
LOG_FILE=logs/testing.log

# Security Configuration
BCRYPT_ROUNDS=10

# Database Configuration (Testing)
DATABASE_URL=https://your-testing-project.supabase.co
DATABASE_HOST=db.supabase.co
DATABASE_PORT=5432
DATABASE_NAME=postgres
DATABASE_USER=postgres
DATABASE_PASSWORD=your-testing-supabase-password

# Redis Configuration (Testing - using in-memory for testing)
REDIS_URL=redis://localhost:6379
REDIS_HOST=localhost
REDIS_PORT=6379

Step 2: Set Up Supabase Testing Project

1. Go to Supabase Dashboard: https://supabase.com/dashboard
2. Create New Project:
   • Name: cim-processor-testing
   • Database Password: Generate a secure password
   • Region: Same as your production project
3. Get API Keys:
   • Go to Settings → API
   • Copy the URL, anon key, and service key
4. Update the configuration with your Supabase credentials

Step 3: Set Up Google Cloud Testing Project

1. Go to Google Cloud Console: https://console.cloud.google.com/
2. Create New Project:
   • Project ID: cim-summarizer-testing
   • Name: CIM Processor Testing
3. Enable APIs:
   • Document AI API
   • Cloud Storage API
   • Cloud Functions API
4. Create Service Account:
   • Go to IAM & Admin → Service Accounts
   • Create service account: cim-testing-service
   • Download JSON key and save as backend/serviceAccountKey-testing.json
5. Create Storage Buckets:

   gsutil mb gs://cim-processor-testing-uploads
   gsutil mb gs://cim-processor-testing-processed
   

6. Create Document AI Processor:

   gcloud documentai processors create \
     --display-name="CIM Testing Processor" \
     --type=FORM_PARSER_PROCESSOR \
     --location=us
   

Step 4: Get LLM API Key

Use the same Anthropic API key as your production environment.

Step 5: Set Up Email Configuration

1. Gmail App Password:
   • Go to Google Account settings
   • Security → 2-Step Verification → App passwords
   • Generate app password for testing
2. Update email configuration in the environment file

🚀 Quick Setup Commands

Once you have all the credentials, run these commands:

# 1. Create the environment file
nano backend/.env.testing
# Paste the configuration above and update with your credentials

# 2. Make deployment script executable
chmod +x deploy-testing.sh

# 3. Run the deployment
./deploy-testing.sh

🧪 What You'll Get

After deployment, you'll have:

• ✅ Cost Monitoring System: Real-time cost tracking and alerts
• ✅ Document Analysis Caching: 20-40% cost reduction for similar documents
• ✅ Microservice Architecture: Scalable, independent document processing
• ✅ 15 New API Endpoints: Cost, cache, and microservice management
• ✅ Database Schema Updates: 6 new tables with triggers and indexes
• ✅ Enhanced Logging: Debug-level logging for testing
• ✅ Performance Tracking: Detailed metrics for analysis

📊 Testing URLs

After deployment, you can test at:

• Frontend: https://cim-summarizer-testing.web.app
• API Base: https://cim-summarizer-testing.web.app
• Health Check: https://cim-summarizer-testing.web.app/health
• Cost Metrics: https://cim-summarizer-testing.web.app/api/cost/user-metrics
• Cache Stats: https://cim-summarizer-testing.web.app/api/cache/stats
• Microservice Health: https://cim-summarizer-testing.web.app/api/processing/health

🔍 Need Help?

If you need help with any of these steps:

1. Supabase Setup: See FIREBASE_TESTING_ENVIRONMENT_SETUP.md
2. Google Cloud Setup: Follow the GCP documentation
3. Deployment Issues: Check TESTING_DEPLOYMENT_GUIDE.md
4. Configuration Issues: Review this guide and update credentials

---

🎉 Ready to deploy Week 8 features! Complete the setup above and run ./deploy-testing.sh