-
Notifications
You must be signed in to change notification settings - Fork 0
Expand file tree
/
Copy path.env.example
More file actions
27 lines (22 loc) · 1.23 KB
/
.env.example
File metadata and controls
27 lines (22 loc) · 1.23 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
# ============================================================================
# Bridle embed example — local config
# Copy this file to `.env` and fill in the values for your Ranch deployment.
# ============================================================================
# Ranch hub origin. Default points at a local Ranch API; override if your hub
# runs elsewhere (e.g. https://ranch.example.com).
RANCH_API_URL=http://localhost:3333
# Ranch API key with permission to mint embed JWTs. Create one in the Ranch
# admin UI (Settings → API Keys). The key never reaches the browser — this
# example's server uses it to call POST /auth/embed/token on the hub.
RANCH_API_KEY=rk_replace_me
# Agent (= Bridle bot) id the embed connects to. Find it in the Ranch admin
# UI on the agent's detail page. The example page passes this to the SDK
# via `data-agent-id`.
BRIDLE_AGENT_ID=agent-replace-me
# Embed JWT lifetime. Format: <n>(s|m|h|d). Bridle's default is 15m which is
# painful for dev — a refresh after lunch shows "token expired". 7 days is
# fine for local testing; tighten it for anything user-facing.
RANCH_EMBED_TOKEN_TTL=7d
# Port the example server listens on. Open http://localhost:$PORT in a
# browser once everything is running.
PORT=8787