Repository navigation
Expand file tree
/
Copy path.env.deploy.example
More file actions
59 lines (53 loc) · 3.21 KB
/
Copy path.env.deploy.example
File metadata and controls
59 lines (53 loc) · 3.21 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
51
52
53
54
55
56
57
58
59
# Copy to `.env.deploy` (gitignored via `.env.*`) and fill in.
# Used by: `npm run deploy`, `npm run deploy:worker`, etc. (see scripts/deploy.mjs)
#
# Prereqs: `npx wrangler login`, `cd server && npx partykit login`
# --- Cloudflare Pages (required for deploy:pages / deploy:all)
# Project slug as shown in Cloudflare Dashboard → Pages
# Must match `name` in root `wrangler.toml` (Wrangler Pages validation).
CF_PAGES_PROJECT_NAME=imposter-game
# If this Pages project is also connected to Git, set this to your production branch (usually main)
# so this upload updates the same production URL as the dashboard. Otherwise you may still see
# an old Git-built bundle (without VITE_*) on https://YOUR_PROJECT.pages.dev while only the
# one-off deployment URL from the CLI log has the correct build.
# CF_PAGES_BRANCH=main
# Baked into the Vite client at build time (no protocol on Partykit host)
# Git-connected Pages: also set the same keys under [vars] in root wrangler.toml (dashboard vars
# often do not reach npm run build when pages_build_output_dir is in that file).
VITE_DISCORD_CLIENT_ID=
VITE_PARTYKIT_HOST=your-party.yourlogin.partykit.dev
# Full URL to Worker token endpoint (use after first worker deploy)
VITE_DISCORD_TOKEN_URL=https://imposter-discord-oauth.your-subdomain.workers.dev/api/token
# When Partykit JOIN_JWT_REQUIRED=true: mint join JWT from Worker (/api/party-jwt); map that path in Discord URL mappings
# VITE_USE_PARTY_JWT=true
# --- Optional: Supabase (website cloud profile, round history, saved word lists)
# Baked into the client at build time — for Git builds, mirror into wrangler.toml [vars] (or dashboard
# may not reach vite build); CLI deploy reads this file.
# Use exactly one key line (anon JWT or a publishable key from the Supabase dashboard).
# VITE_SUPABASE_URL=https://xxxx.supabase.co
# VITE_SUPABASE_ANON_KEY=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9...
# VITE_SUPABASE_PUBLISHABLE_DEFAULT_KEY=sb_publishable_...
# VITE_SUPABASE_PUBLISHABLE_KEY=sb_publishable_...
# --- Cloudflare Worker — Discord OAuth token exchange
# Pushed as encrypted Worker secrets (`wrangler secret put`). Must match your Discord app.
DISCORD_CLIENT_ID=
DISCORD_CLIENT_SECRET=
# Optional if Discord returns invalid_grant (must match Developer Portal redirect)
# DISCORD_REDIRECT_URI=
# --- Partykit — injected on each `partykit deploy` via --var
# Optional: comma-separated full origins (scheme + host, no path) allowed to open WebSockets.
# Empty = allow any origin (default). Production example for your custom domain:
# ALLOWED_WEB_ORIGINS=https://imposter-game.site,https://www.imposter-game.site
# Discord Activity uses https://<CLIENT_ID>.discordsays.com — allowed automatically unless:
# ALLOW_DISCORD_ACTIVITY_ORIGINS=false
ALLOW_DISCORD_ACTIVITY_ORIGINS=true
JOIN_VERIFY=false
# Reject host custom words containing blocked tokens (see server/src/word-profanity.ts)
WORD_PROFANITY_FILTER=false
# Optional: require short-lived join JWT (must match Worker PARTYKIT_JWT_SECRET)
JOIN_JWT_REQUIRED=false
JOIN_JWT_SECRET=
# --- Worker secret (wrangler secret put) — signs /api/party-jwt; must equal JOIN_JWT_SECRET on Partykit
# PARTYKIT_JWT_SECRET=
# Optional override for `partykit deploy -n` (defaults to partykit.json name)
# PARTYKIT_DEPLOY_NAME=