feat: Add Render.com deployment support with production data
Render Configuration: - render.yaml for declarative deployment - requirements-dashboard.txt (lightweight deps for cloud) - Updated .streamlit/config.toml for production - Updated app.py to auto-detect production vs local data Production Data: - Added data/production/test-07/ with 30 real call analyses - Updated .gitignore to allow data/production/ Documentation: - Added Render.com section to DEPLOYMENT.md with step-by-step guide Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
This commit is contained in:
@@ -4,6 +4,7 @@ Rich visualization dashboard for call analysis results.
|
||||
Following Beyond Brand Identity Guidelines v1.0
|
||||
"""
|
||||
|
||||
import os
|
||||
import sys
|
||||
from pathlib import Path
|
||||
from datetime import datetime
|
||||
@@ -82,7 +83,17 @@ def main():
|
||||
st.markdown("---")
|
||||
|
||||
# Batch selector
|
||||
data_dir = Path(__file__).parent.parent / "data" / "output"
|
||||
# On Render (production), use data/production; locally use data/output
|
||||
base_path = Path(__file__).parent.parent / "data"
|
||||
if os.environ.get("RENDER") or (base_path / "production").exists():
|
||||
# Check production first (has committed data for cloud)
|
||||
prod_path = base_path / "production"
|
||||
if prod_path.exists() and any(prod_path.iterdir()):
|
||||
data_dir = prod_path
|
||||
else:
|
||||
data_dir = base_path / "output"
|
||||
else:
|
||||
data_dir = base_path / "output"
|
||||
|
||||
batches = get_available_batches(data_dir)
|
||||
|
||||
|
||||
Reference in New Issue
Block a user