.env.example

# copy to `.env` and fill in. loaded by the justfile (`set dotenv-load`) and
# baked into the firmware at build time, so the `clock` recipe re-touches the
# example to force a recompile when these change.

# wifi credentials for the t5s3 clock example
SSID=your-wifi-name
PASSWORD=your-wifi-password

# timezone offset from UTC in hours (e.g. -7 for PDT, -8 for PST, +1 for CET)
# for t5s3 ui; can be changed at runtime via settings page
TZ_OFFSET_HOURS=-7

# noot-server address for the t5s3 ui music, environment, and gps map-tile
# fetches. SERVER_HOST may be an IP or a hostname (resolved over DNS);
# SERVER_PORT defaults to 3009.
SERVER_HOST=192.168.1.100
SERVER_PORT=3009

# tailscale funnel hostname for reaching noot-server away from home (the
# machine's ts.net name, served publicly via `tailscale funnel 3009`). when
# set, all noot-server traffic — music, environment, map tiles — goes to it
# over verified https (pinned let's encrypt root) instead of plain http to
# SERVER_HOST. requires SERVER_TOKEN, since the funnel endpoint is reachable
# by the whole internet. replaces the old TAILNET_HOST / termux-proxy setup.
# FUNNEL_HOST=machine.tailnet.ts.net

# bearer token sent with every noot-server request when set; noot-server must
# require it once exposed via funnel. use a long random value, e.g.:
#   openssl rand -base64 32
# SERVER_TOKEN=changeme

# meshnet-wide symmetric key (chacha20-poly1305) sealing every nootmesh
# packet; 64 hex chars = 32 bytes, identical on every node. unset builds fall
# back to a public dev key (fine for the bench, no confidentiality). generate:
#   openssl rand -hex 32
# MESH_KEY=changeme

# the environment page needs no configuration: it lists every sensor device
# noot-server knows about (GET /api/sensors), air and water alike.

# the weather page needs no configuration: it fetches a public forecast (from
# open-meteo.com, keyless, over verified https) for the device's current GPS
# position, so it requires the `gps` feature and a position fix.