Skip to content

Record a sky camera around the clock, keep the footage on your own disk, and find what flew past.

2.7 KB
Raw Blame
# Copy to .env and fill in. .env is git-ignored.
# Keep comments on their own lines: values are read verbatim.

# Camera (Dahua) web API, used by camera_mcp.py
CAMERA_IP_ADDRESS=203.0.113.10
CAMERA_SCHEME=https
CAMERA_PORT=443
CAMERA_USERNAME=admin
CAMERA_PASSWORD=change-me

# Camera RTSP port and stream path, used by the relay. The default path is Dahua's main stream; other
# cameras use their own, for example /Streaming/Channels/101 (Hikvision) or /stream1 (TP-Link Tapo).
CAMERA_RTSP_PORT=554
CAMERA_RTSP_PATH='/cam/realmonitor?channel=1&subtype=0'

# Relay: camera id used in object keys, and the ingest Worker it uploads to
CAM_ID=sky01
INGEST_URL=https://skyvision-ingest.<your-subdomain>.workers.dev

# Worker secret (same value as `wrangler secret put INGEST_TOKEN`); kept here for manual API calls.
# deploy.sh does not copy it: the Pi keeps its own copy in ~/.config/skyvision/ingest.env.
INGEST_TOKEN=generate-with-openssl-rand-hex-32

# Relay: never let the Pi's disk drop below this many GB free (default 20)
MIN_FREE_GB=20

# Your Workers deployment. `npm run config` (run by every wrangler script in package/dashboard and
# package/worker) fills these into wrangler.deploy.json; in Workers Builds, set them as build variables.
# Website host (protected by your Access application) and API host: two custom domains on your zone.
SITE_HOST=sky.example.com
API_HOST=api.sky.example.com
# The Access application on SITE_HOST: your team domain and the application's audience (AUD) tag.
ACCESS_TEAM_DOMAIN=https://<team>.cloudflareaccess.com
ACCESS_AUD=<application-audience-tag>
# Comma-separated camera ids the relay may upload for (CAM_ID above is one of them).
CAMERAS=sky01
# The Workers VPC service in front of the footage store's tunnel (npm run wrangler -- vpc service list).
STORE_SERVICE_ID=<vpc-service-id>
# Optional for deploys (the database is found by name); needed by `npm run dev`, which uses your real
# catalog: npm run wrangler -- d1 info skyvision-catalog
D1_DATABASE_ID=
# Optional: the host for the documentation site (package/docs), if you publish it with `npm run deploy` there.
DOCS_HOST=

# Written by the guided setup (npm run setup), which also fills in everything above except CAMERA_SCHEME,
# CAMERA_PORT, MIN_FREE_GB and DOCS_HOST (their defaults apply). Hosts are SSH hosts.
# Cloudflare account, when your login has more than one.
CLOUDFLARE_ACCOUNT_ID=
# The footage store: its SSH host, footage folder, whether that folder is on the system disk, and its tunnel.
STORE_HOST=
STORE_ROOT=
STORE_SYSTEM_DISK=no
STORE_TUNNEL_ID=
# The relay's SSH host.
RELAY_HOST=
# The processor's SSH host and device name, and an Agent key for every camera (setup registers the
# processor with it; scripts can use it too).
PROCESSOR_HOST=
PROCESSOR_DEVICE=
OPENSKYCAM_AGENT_KEY=