/
githubmirror
/
novu
Обзор
Документация
Войти
/
githubmirror
/
novu
Код
Запросы
0
Пакеты
0
Релизы
0
Аналитика
Безопасность
next
apps/dashboard/.example.env
69 строк
3 KB
Adam Chmara
refactor(root): rename web_chat platform to agent_chat fixes NV-8553 (#12325)
12 авг 2026, 17:12
Не верифицирован
12 авг 2026, 17:12
db81656
Код
Авторство
О чём код?
VITE_SENTRY_DSN= VITE_LAUNCH_DARKLY_CLIENT_SIDE_ID= # Provider-managed MCP ("Add from Claude"). Vite env fallback when LD client id is unset. # VITE_IS_MCP_PROVIDER_MANAGED_ENABLED=true # WhatsApp Embedded Signup (Meta Tech Provider). Vite env fallback when LaunchDarkly client is unset. # VITE_IS_WHATSAPP_EMBEDDED_SIGNUP_ENABLED=true # Meta app + Embedded Signup configuration identifiers the dashboard needs to launch the flow. VITE_NOVU_WHATSAPP_APP_ID= VITE_NOVU_WHATSAPP_CONFIG_ID= # Agent overview "What's next" section. Vite env fallback when LD client id is unset. # VITE_IS_AGENT_WHATS_NEXT_ENABLED=true # MS Teams subscriber-rollout "What's next" guide + post-connect rollout CTA. Vite env fallback when LD client id is unset. # VITE_IS_AGENT_MSTEAMS_WHATS_NEXT_ENABLED=true # Email agent production-readiness "What's next" guide + simplified out-of-box setup. Vite env fallback when LD client id is unset. # VITE_IS_AGENT_EMAIL_WHATS_NEXT_ENABLED=true # Agent agent chat channel (pre-release). Keep off to hide the Agent Chat channel from every picker. Vite env fallback when LD client id is unset. # VITE_IS_AGENT_WEB_CHAT_ENABLED=true # Workflow agent assignment ("Send & reply via agent"). Vite env fallback when LD client id is unset. # VITE_IS_WORKFLOW_AGENT_ASSIGNMENT_ENABLED=true VITE_HUBSPOT_EMBED= VITE_API_HOSTNAME=http://localhost:3000 # VITE_AGENT_API_HOSTNAME=https://your-tunnel.ngrok.app VITE_WEBSOCKET_HOSTNAME=http://localhost:3002 VITE_CLERK_PUBLISHABLE_KEY= VITE_NOVU_APP_ID= VITE_GTM= VITE_SELF_HOSTED= VITE_PLAIN_SUPPORT_CHAT_APP_ID= VITE_NOVU_ENTERPRISE=false # Multi-Region Configuration # List of region codes (comma-separated). FIRST region is the base/default region. # Use SHORT codes that match your env var suffixes (e.g., 'sg' not 'singapore') # The base region uses env vars WITHOUT suffix (VITE_API_HOSTNAME, not VITE_API_HOSTNAME_XX) VITE_REGIONS=us,sg # Base Region - NO suffix required (everything uses base env vars) VITE_DASHBOARD_URL=http://localhost:4201 # VITE_API_HOSTNAME and VITE_WEBSOCKET_HOSTNAME are already defined above VITE_AWS_REGION=us-east-1 # VITE_REGION_NAME=US # VITE_REGION_FLAG=🇺🇸 # Additional Region Configuration # For each additional region, add variables with _REGIONCODE suffix (uppercase): # Singapore Region VITE_DASHBOARD_URL_SG=http://localhost:4202 VITE_API_HOSTNAME_SG=http://localhost:3200 VITE_WEBSOCKET_HOSTNAME_SG=http://localhost:3003 VITE_AWS_REGION_SG=ap-southeast-1 VITE_REGION_NAME_SG=Singapore VITE_REGION_FLAG_SG=🇸🇬 # To add more regions, follow this pattern: # VITE_DASHBOARD_URL_<CODE>=<url> # VITE_API_HOSTNAME_<CODE>=<url> # VITE_WEBSOCKET_HOSTNAME_<CODE>=<url> # VITE_AWS_REGION_<CODE>=<aws-region> # VITE_REGION_NAME_<CODE>=<display-name> # VITE_REGION_FLAG_<CODE>=<emoji-flag> # See MULTI_REGION_SETUP.md for detailed instructions # When using `pnpm dev:portless`, scripts/portless-dev-env.mjs resolves these at # runtime via `portless get` (worktree-prefixed and proxy-port aware): # VITE_API_HOSTNAME, VITE_WEBSOCKET_HOSTNAME, VITE_DASHBOARD_URL, VITE_BETTER_AUTH_BASE_URL # # Run `PORTLESS=0 pnpm start:dashboard` to bypass the proxy without uninstalling.