Files
2026-07-13 13:36:53 +08:00

34 lines
1.5 KiB
Bash

# Hermes Analytics Configuration (optional)
# Set these in your build environment or CI to enable analytics.
# These values are NOT exposed to users — analytics only works in official builds.
#
# GITHUB SECRETS SETUP:
# 1. Go to Settings → Secrets and variables → Actions
# 2. Add repository secrets:
# - VITE_ANALYTICS_BASE_URL - Base URL of the analytics service
# (e.g. https://analytics.hermesone.org)
# - VITE_ANALYTICS_API_KEY - API key sent as the x-api-key header
# 3. These are automatically injected during GitHub Actions builds.
# 4. Forks without these secrets will have analytics disabled.
VITE_ANALYTICS_BASE_URL=https://analytics.hermesone.org
VITE_ANALYTICS_API_KEY=your_analytics_api_key_here
# Hermes One Backend Configuration (optional)
# Base URL + client key for device login and desktop↔backend agent sync.
# The MAIN_VITE_ prefix scopes these to the main process (where the API calls
# run) so the key isn't also copied into the renderer bundle.
#
# GITHUB SETUP (injected during GitHub Actions builds):
# - Repository VARIABLE HERMES_API_URL → MAIN_VITE_HERMES_API_URL
# - Repository SECRET HERMES_API_KEY → MAIN_VITE_HERMES_API_KEY
#
# Local dev: leave the URL at the Nitro dev server and the key empty (the
# backend doesn't enforce the key yet). Runtime HERMES_API_URL / HERMES_API_KEY
# override these baked values.
MAIN_VITE_HERMES_API_URL=http://localhost:3002
MAIN_VITE_HERMES_API_KEY=your_hermes_api_key_here