-
Notifications
You must be signed in to change notification settings - Fork 0
Expand file tree
/
Copy path.env.example
More file actions
41 lines (33 loc) · 1.56 KB
/
Copy path.env.example
File metadata and controls
41 lines (33 loc) · 1.56 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
# Copy this file to .env.local and fill in the real values.
# .env.local is gitignored - it never gets committed.
# ---- Supabase (database + auth) ----
# Get these from your Supabase project settings → API
NEXT_PUBLIC_SUPABASE_URL=https://your-project-id.supabase.co
NEXT_PUBLIC_SUPABASE_ANON_KEY=your-anon-key-here
SUPABASE_SERVICE_ROLE_KEY=your-service-role-key-here
# ---- Anthropic (Claude API for signal extraction + summarization) ----
# Greg is rationing these - ask him for a project key
ANTHROPIC_API_KEY=sk-ant-...
# ---- Slack (webhook for posting the digest and alerts) ----
# Create at https://api.slack.com/messaging/webhooks
# For dev, point this at a test channel in your own Slack workspace
SLACK_WEBHOOK_URL=https://hooks.slack.com/services/...
# Channel for the weekly digest (separate from urgent alerts so we can A/B in dev)
SLACK_DIGEST_CHANNEL=#account-intel
SLACK_ALERTS_CHANNEL=#account-intel-urgent
# ---- News & data sources ----
# NewsAPI - free tier is fine for development
# https://newsapi.org
NEWSAPI_KEY=your-newsapi-key-here
# Optional: Bing Web Search (better for hospital-specific queries)
# Leave blank if not using
BING_SEARCH_KEY=
# ---- Operational ----
# 'development' | 'staging' | 'production'
NODE_ENV=development
# How often the agent runs the continuous-monitoring loop (in minutes)
# Production target: 60. Development: 5 so you can see it working.
MONITOR_INTERVAL_MINUTES=5
# How often the weekly digest is generated (cron format)
# Mondays at 8 AM ET. In dev, override to '*/2 * * * *' to fire every 2 min for testing.
DIGEST_CRON=0 8 * * 1