.env.example

# Alibaba Cloud Model Studio credentials for the China (Beijing) region.
# Keep these server-side. Never expose them through VITE_* variables.
DASHSCOPE_API_KEY=
DASHSCOPE_WORKSPACE_ID=

# Optional upstream overrides.
DASHSCOPE_MODEL=qwen-audio-3.0-realtime-plus
# DASHSCOPE_REALTIME_URL=

# Feedback, catalog draft generation, and success detection use a non-thinking
# text model through DashScope's OpenAI-compatible endpoint. They reuse the key.
DASHSCOPE_FEEDBACK_MODEL=qwen3.6-flash
# DASHSCOPE_FEEDBACK_URL=https://dashscope.aliyuncs.com/compatible-mode/v1/chat/completions
# DASHSCOPE_FEEDBACK_TIMEOUT_MS=60000

SERVER_HOST=0.0.0.0
SERVER_PORT=3001
CLIENT_ORIGIN=http://localhost:5173
LOG_LEVEL=info

# Production/Docker serves the Vite build from this same Node process.
# SERVE_STATIC=true
# STATIC_CLIENT_PATH=dist/client

# Optional direct HTTPS termination. Configure both PEM paths or neither.
# TLS_CERT_PATH=/app/certs/fullchain.pem
# TLS_KEY_PATH=/app/certs/privkey.pem

# Docker Compose interpolates these deployment-only values. PUBLIC_ORIGIN must
# be the exact externally visible origin, without a trailing slash.
# PUBLIC_ORIGIN=https://role-player.example.com
# TLS_CERT_HOST_PATH=./certs
# HTTPS_PORT=443
# ROLE_PLAYER_DATA_VOLUME=role-player-data

# SQLite database files. Relative paths resolve from the process working directory.
CATALOG_DATABASE_PATH=data/catalog.sqlite
CONVERSATION_DATABASE_PATH=data/conversations.sqlite

# Source used only by `pnpm database:split` when migrating the old one-file layout.
LEGACY_DATABASE_PATH=data/role-player.sqlite