Jason Tudisco
927d106eae
- Add `SEARCH_PROVIDER` config with Tavily/Brave API key validation in server and prod script - Introduce unified `web_search` tool and shared search service with Tavily + Brave backends - Update chat UI tool status/result labels to treat both search tools consistently
25 lines
511 B
Plaintext
25 lines
511 B
Plaintext
# Server
|
|
BIND_ADDR=0.0.0.0:3001
|
|
RUST_LOG=info
|
|
|
|
# Database
|
|
DATABASE_URL=sqlite:chat.db?mode=rwc
|
|
|
|
# Auth
|
|
JWT_SECRET=change-me-to-a-random-secret
|
|
|
|
# OpenRouter API
|
|
OPENROUTER_API_KEY=sk-or-v1-your-key-here
|
|
|
|
# Search provider: tavily or brave
|
|
SEARCH_PROVIDER=tavily
|
|
|
|
# Tavily Search API
|
|
TAVILY_API_KEY=tvly-your-key-here
|
|
|
|
# Brave Search API (optional unless SEARCH_PROVIDER=brave)
|
|
BRAVE_API_KEY=your-brave-api-key-here
|
|
|
|
# Production: path to built client files (default: ../client/dist)
|
|
# STATIC_DIR=../client/dist
|