.env.example

# Public base URL of the R2 bucket that pipeline/publish.py uploads to.
#
# Artifacts are flat keys at the bucket root, so the client appends names like
# `background.pmtiles` and `trails.geojson` directly to this. No trailing slash
# is needed - one is stripped either way.
#
# Get the value from Cloudflare -> R2 -> your bucket -> Settings -> Public
# access. Either enable the r2.dev subdomain (fine for testing, rate-limited
# and not intended for production traffic) or connect a custom domain.
#
# Vite inlines this at BUILD time and only exposes variables prefixed VITE_,
# so changing it means rebuilding and redeploying - it is not read at runtime.
#
# Copy this file to `.env.local` for local use, and set the same variable in
# your host's build settings (Cloudflare Pages / Vercel / Netlify) for deploys.
VITE_DATA_BASE_URL=https://pub-example.r2.dev

# The Supabase project that signs hikers in (features/AUTHENTICATION.md).
#
# Only contributing needs an account. With these unset the app builds and runs
# exactly as before - the map, water, shelters, closures and warnings all work
# - and the sign-in controls report that this build has no project rather than
# offering a round trip that cannot finish.
#
# Get both from Supabase -> Project Settings -> API. The anon key is meant to
# be public and ships in the bundle; the JWT secret is NOT one of these and
# belongs only in the backend's environment (see backend/README.md).
#
# Inlined at BUILD time like the variable above, so changing either means a
# rebuild and redeploy.
VITE_SUPABASE_URL=https://your-project-ref.supabase.co
VITE_SUPABASE_ANON_KEY=your-anon-public-key

# Which sign-in buttons this build offers, comma separated, from `google`,
# `apple` and `email`. Defaults to `google,email`.
#
# It is a setting because the three do not cost the same to switch on: email
# needs nothing, Google needs a Cloud Console registration, and Apple needs a
# $99/yr Developer Program membership and a Services ID. Each one listed here
# must actually be configured in Supabase -> Authentication -> Providers, or
# its button reaches an error page instead of an account. Unknown names are
# ignored.
VITE_AUTH_PROVIDERS=google,email

# The OurHike backend that receives queued reports (#231).
#
# Distinct from the R2 bucket above: that one serves static published data a
# hiker downloads once and reads offline forever, this is a live API reachable
# only with signal. Distinct from Supabase too - a hiker signs in THERE, and
# this backend only verifies the token that comes back.
#
# With it unset the app builds and runs exactly as before: the map, water,
# shelters and downloads all work, reports still queue in the outbox with their
# authored timestamps, and nothing is lost - they simply wait for a build that
# has somewhere to send them. That is the current state of every deploy, since
# the backend is not deployed anywhere yet (#95).
#
# No trailing slash is needed; one is stripped either way. Inlined at BUILD
# time like everything above.
VITE_API_BASE_URL=https://api.example.org