-
Notifications
You must be signed in to change notification settings - Fork 0
Expand file tree
/
Copy path.env.example
More file actions
24 lines (20 loc) · 1.15 KB
/
Copy path.env.example
File metadata and controls
24 lines (20 loc) · 1.15 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
# Copy to .env.local and fill in your own workspace id.
#
# None of this is secret: these are public identifiers and public URLs. Your
# Zite session lives in a cookie on the runtime origin, not in this file.
#
# Running locally still needs a Zite workspace: the Vite dev server serves the
# frontend, but every endpoint in src/api/ executes on Zite's runtime against
# your workspace database. See "Local development" in the README.
# The workspace database this monorepo is bound to. Find it in your workspace
# URL, or ask your agent for the workspace id after it installs this template.
ZITE_BASE_ID=your-workspace-id
# Which Zite runtime the generated caller targets.
VITE_ZITE_ENV=production
# Injects the signed-in user and window._ziteUsageToken into the page. Served
# from the org's own origin so it sees that origin's session.
VITE_APP_RUNTIME_URL=https://zite.com/app-runtime.js
# REQUIRED LOCALLY. In a browser the generated caller defaults to same-origin
# "/api/<name>", which the Vite dev server cannot serve, so every endpoint call
# 404s. This switches it to direct mode: <runner>/public/<appId>/api/<name>.
VITE_ZITE_RUNNER_URL=https://workflows.zite.com