Ben Stull
6cfbf69e26
Mid-Session-L correction to the v0.15.0 release that the dispatched
subagent (Session ξ) shipped. ξ was working from a pre-vendor brief
that specified @amplitude/analytics-browser and treated the API key
as a secret via `flotilla secret set`. Operator subsequently
provisioned the Amplitude project, surfaced the vendor's
recommended installation prompt, and confirmed the key value.
Three downstream changes:
- Package: swap @amplitude/analytics-browser → @amplitude/unified
(analytics + session replay in one install; vendor-recommended).
- Init call: `amplitude.init(KEY, undefined, { defaultTracking: false })`
becomes `amplitude.initAll(KEY, { analytics: { autocapture: true },
sessionReplay: { sampleRate: 1 } })`. Vendor's exact installation-
wizard shape; gates remain on the v0.13.0 consent banner.
- Binding: Amplitude browser keys are bundle-embedded by design
(same nature as VITE_TURNSTILE_SITE_KEY from v0.12.0), so the key
is public, not secret. CHANGELOG MUST step rewritten to bind via
`flotilla overlay set <deployment> VITE_AMPLITUDE_API_KEY=<key>`
rather than `flotilla secret set`. The roadmap row #13's
"new secret: AMPLITUDE_API_KEY" wording predated vendor
consultation; the roadmap will be updated when this ships.
§19.2 candidate captured in CHANGELOG: split the analytics consent
toggle into a separate session-replay category (recording has a
larger privacy footprint than event counters), follow-up release.
Wrapper structural shape (track/identify/anonymize, queue + drain,
consent-flip → setOptOut, lazy import) is unchanged from ξ's work.
Event taxonomy and Login.jsx / App.jsx / Admin.jsx / etc. instrument
sites are unchanged. Frontend build verified green
(VITE_APP_NAME=… npm run build).
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
88 lines
4.0 KiB
Bash
88 lines
4.0 KiB
Bash
# Frontend build-time configuration. Copy to `frontend/.env` and fill in.
|
|
#
|
|
# Vite picks up VITE_* variables from these files at build (`npm run build`)
|
|
# and dev (`npm run dev`) time. Real `.env` files are gitignored; only this
|
|
# `.env.example` is committed.
|
|
|
|
# The user-visible name of this deployment. Used as the browser tab title,
|
|
# the header brand, and the landing page H1. Required — the framework
|
|
# ships no default on purpose so each deployment names itself. If unset,
|
|
# `npm run build` fails with a clear message.
|
|
#
|
|
# Examples:
|
|
# VITE_APP_NAME=Wiggleverse RFC
|
|
# VITE_APP_NAME=Wiggleverse Open Human Model
|
|
VITE_APP_NAME=
|
|
|
|
# Optional contact line shown on the /beta-pending page when a deployment
|
|
# is in private-beta mode (i.e. the backend's `allowed_emails` table has
|
|
# rows). Free-text — an email address, a URL, or a one-line instruction
|
|
# tells visitors how to request an invitation. If unset, the page falls
|
|
# back to a generic "contact the deployment operator" line.
|
|
#
|
|
# Examples:
|
|
# VITE_BETA_CONTACT=ben@wiggleverse.org
|
|
# VITE_BETA_CONTACT=DM @ben on Matrix
|
|
VITE_BETA_CONTACT=
|
|
|
|
# Optional URL to the deployment's privacy policy (v0.13.0+, SPEC §14.5).
|
|
# The framework ships a minimal default privacy policy at `/privacy`
|
|
# that describes the framework's stance and lists the cookies the
|
|
# framework sets. When this var is set to an http(s) URL, the page
|
|
# renders the framework's stub above a link to the configured URL —
|
|
# deployments use this to layer their own policy content on top
|
|
# without forking the framework. Unset is OK; the stub is sufficient
|
|
# for a deployment that has nothing specific to add.
|
|
#
|
|
# Examples:
|
|
# VITE_PRIVACY_POLICY_URL=https://wiggleverse.org/privacy
|
|
VITE_PRIVACY_POLICY_URL=
|
|
|
|
# Optional URL to the deployment's cookies policy (v0.13.0+, SPEC §14.6).
|
|
# Same shape as VITE_PRIVACY_POLICY_URL. The framework's default
|
|
# `/cookies` page lists exactly which cookies the framework sets
|
|
# (rfc_session, the consent-choice localStorage entry); a deployment
|
|
# that adds its own cookies (analytics SDK once #13 lands, third-party
|
|
# embeds) points this var at a page that documents the full list.
|
|
# Unset is OK; the stub is sufficient for a default-config deployment.
|
|
#
|
|
# Examples:
|
|
# VITE_COOKIES_POLICY_URL=https://wiggleverse.org/cookies
|
|
VITE_COOKIES_POLICY_URL=
|
|
|
|
# v0.12.0 / roadmap item #10: CloudFlare Turnstile site key (public).
|
|
# Provision a Turnstile site at dash.cloudflare.com → Turnstile → Add
|
|
# site. The site key (this var) is embedded into the frontend bundle at
|
|
# build time and rendered by the Turnstile widget on the /login email-
|
|
# entry step. The secret key (private) lives in the backend env as
|
|
# CLOUDFLARE_TURNSTILE_SECRET — see backend/.env.example. Leave unset
|
|
# in dev to skip the widget; the backend's TURNSTILE_REQUIRED policy
|
|
# decides what happens to a tokenless request.
|
|
#
|
|
# Examples:
|
|
# VITE_TURNSTILE_SITE_KEY=0x4AAAAAAA...
|
|
VITE_TURNSTILE_SITE_KEY=
|
|
|
|
# v0.15.0 / roadmap item #13: Amplitude project API key (public).
|
|
# Embedded in the frontend bundle at build time and used by the
|
|
# analytics wrapper (`frontend/src/lib/analytics.js`) — which loads
|
|
# `@amplitude/unified` (Analytics + Session Replay) when the user
|
|
# has granted analytics consent (v0.13.0 cookie banner). Provision
|
|
# an Amplitude project at app.amplitude.com → Projects → New, copy
|
|
# the API key.
|
|
#
|
|
# Public by design: Amplitude browser keys are bundle-embedded
|
|
# (visible in dev tools), same nature as VITE_TURNSTILE_SITE_KEY
|
|
# (also public; the truly-secret half of that Turnstile pair is
|
|
# CLOUDFLARE_TURNSTILE_SECRET on the backend). For deployments
|
|
# behind flotilla, bind via `flotilla overlay set <deployment>
|
|
# VITE_AMPLITUDE_API_KEY=<key>` — NOT `flotilla secret set`. The
|
|
# vendor's installation wizard shows the key inline as a literal
|
|
# string in the init call, confirming the public framing. Leave
|
|
# unset in dev; the wrapper logs one console warning and no-ops
|
|
# (the app continues to work).
|
|
#
|
|
# Examples:
|
|
# VITE_AMPLITUDE_API_KEY=01234567890abcdef01234567890abcd
|
|
VITE_AMPLITUDE_API_KEY=
|