.env.example

# Optional — the app runs with zero configuration. `pnpm dev` and
# `docker compose up` both boot without this file. These vars only *seed* the
# first boot; afterwards the in-app Config UI owns every value. Copy to .env
# only to override a first-boot default.
#
# Defaults are picked by NODE_ENV: dev writes under <repo>/.dev-data and reaches
# MediaMTX on localhost; production uses the container mounts (/data,
# /recordings, /screenshots) and the compose hostname http://mediamtx.

# The address browsers use to reach this stack. Set this if the browser isn't
# on this machine — a LAN IP or hostname. `docker compose up` feeds it to both
# halves of the "not on this host" trap: MediaMTX's advertised WebRTC hosts
# (MTX_WEBRTCADDITIONALHOSTS, which is why mediamtx.yml has
# webrtcAdditionalHosts commented out) and the app's REMOTE_MEDIAMTX_URL below.
# Leave it unset and everything stays on 127.0.0.1, as before.
#
# Compose-only: it never reaches apps/api/src/env.ts, because the app has no
# use for a bare host. And on an *existing* deployment it seeds nothing — once
# config.json exists the /config UI owns the playback URL, so setting this
# updates the WebRTC host but not the playback URL. Change that one in the UI.
# REMOTE_MEDIAMTX_HOST=192.168.1.50

# MediaMTX API, as reached from the machine running the api
# BACKEND_SERVER_MEDIAMTX_URL=http://127.0.0.1
# MEDIAMTX_API_PORT=9997

# Playback URL the browser uses to reach MediaMTX. Under compose this is
# derived from REMOTE_MEDIAMTX_HOST — set that instead.
# REMOTE_MEDIAMTX_URL=http://localhost

# Where the api reads recordings/screenshots and writes config.json. Defaults
# to <repo>/.dev-data/* in dev. Relative overrides resolve against the api's
# working directory (apps/api in dev) — use absolute paths to avoid surprises.
# DATA_DIR=/abs/path/data
# MEDIAMTX_RECORDINGS_DIR=/abs/path/recordings
# MEDIAMTX_SCREENSHOTS_DIR=/abs/path/screenshots

# LOG_LEVEL=info