-
Notifications
You must be signed in to change notification settings - Fork 154
Expand file tree
/
Copy path.env.example
More file actions
50 lines (46 loc) · 2.47 KB
/
Copy path.env.example
File metadata and controls
50 lines (46 loc) · 2.47 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
42
43
44
45
46
47
48
49
50
# Sokuji Frontend Environment Variables
# Copy this file to .env and fill in your values
# Backend Base URL (without /api suffix)
# This is the base URL for your Cloudflare Workers backend
# Better Auth will append /api/auth automatically
# For API calls, code uses getApiUrl() which appends /api
# For local development: http://localhost:8787
# For production: https://sokuji.kizuna.ai
VITE_BACKEND_URL=http://localhost:8787
# Master gate for Kizuna AI (true/false). Governs the account UI, onboarding's
# account step, and whether ANY managed provider is registered. Turning it off
# makes this a non-Kizuna build; it cannot hold back an individual provider.
VITE_ENABLE_KIZUNA_AI=true
# One gate per Kizuna-managed provider, because they are released
# independently. Each is ANDed with the master gate above.
#
# They bill on different models — the relay twins per second of session time,
# Soniox on reported usage — and the wallet page publishes one set of rates at
# a time, so shipping a provider before its rates are up charges a user at one
# rate while showing them another.
#
# FALSE here on purpose. This file is meant to be copied to .env (see the top),
# including for release builds, so a `true` sample would hand every copier the
# configuration these gates exist to prevent. Development ignores the values
# anyway: each helper returns true whenever DEV is set.
#
# Adding a gate here is not enough to make it reach a build — it must also be
# forwarded in extension/vite.config.ts's `define` list and in every build step
# of .github/workflows/build.yml. featureGateForwarding.consistency.test.ts
# fails when either is missed.
#
# In CI these come from repository VARIABLES, not secrets (`vars.X`, not
# `secrets.X`). They are not secret — the value is compiled into the published
# client — and GitHub redacts secret values throughout the build log, so a
# secret set to `true` censors that word everywhere. Variables also print their
# values in `gh variable list`, which is how you confirm what a release will
# offer before tagging it. v0.36.3 shipped with the whole Kizuna family off
# because the values were set as variables while the workflow read secrets.
VITE_ENABLE_KIZUNA_SONIOX=false
VITE_ENABLE_KIZUNA_OPENAI_TRANSLATE=false
VITE_ENABLE_KIZUNA_VOLCENGINE_AST2=false
# PostHog Analytics Configuration
# Set VITE_POSTHOG_KEY to enable analytics tracking
# Leave empty or unset to disable analytics (recommended for forks)
VITE_POSTHOG_KEY=
VITE_POSTHOG_HOST=https://us.i.posthog.com