forked from BasedHardware/omi
-
Notifications
You must be signed in to change notification settings - Fork 0
Expand file tree
/
Copy path.env.example
More file actions
39 lines (32 loc) · 2.02 KB
/
Copy path.env.example
File metadata and controls
39 lines (32 loc) · 2.02 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
# Copy to .env and fill in. .env is gitignored.
# Firebase — Omi's public web config (project: based-hardware).
# These values let the app authenticate against the same Firebase project that
# the Omi macOS/web apps use, so any Omi account works for sign-in.
# Discovered via: GET https://www.googleapis.com/identitytoolkit/v3/relyingparty/getProjectConfig?key=<API_KEY>
VITE_FIREBASE_API_KEY=AIzaSyD9dzBdglc7IO9pPDIOvqnCoTis_xKkkC8
VITE_FIREBASE_AUTH_DOMAIN=based-hardware.firebaseapp.com
VITE_FIREBASE_PROJECT_ID=based-hardware
# Omi backend base URLs
VITE_OMI_API_BASE=https://api.omi.me
VITE_OMI_DESKTOP_API_BASE=https://desktop-backend-hhibjajaja-uc.a.run.app
# PostHog analytics — same project the macOS desktop app reports to. Both have
# sensible defaults baked in (the key is a publishable client key), so these only
# need setting to point at a different PostHog project.
# PostHog host is fixed in analytics.ts to match renderer CSP (us.i.posthog.com).
# VITE_POSTHOG_HOST is not read at runtime.
VITE_POSTHOG_KEY=phc_z3qUFhGUgYIOMYnfxVSrLmYISQvbgph8iREQv3sez3Y
# Omi developer API key — required for POST /v1/dev/user/conversations/from-segments
# (cloud sync of recorded conversations). Generate one in your Omi app under
# Settings → Developer → Create API key. If unset, recordings save locally only.
VITE_OMI_API_KEY=
# Google integration (parity 3d). Copy this file to `.env` and fill in real values.
# Desktop OAuth client id from Google Cloud Console (an OAuth 2.0 "Desktop app" client).
# Read by the MAIN process (electron-vite MAIN_VITE_ prefix).
MAIN_VITE_GOOGLE_CLIENT_ID=
# Client secret for the same Desktop client. Google's Desktop clients require it
# at the token endpoint even with PKCE. Main-process only; never exposed to the
# renderer. Leave blank only if your client type genuinely needs no secret.
MAIN_VITE_GOOGLE_CLIENT_SECRET=
# Show the Google integration in Settings ('1' = on). Read by the RENDERER.
# Leave unset/'0' for non-test builds until Google verification is granted.
VITE_ENABLE_GOOGLE_INTEGRATION=0