.env.harness.example

# .env.harness.example — template for harness runs.
#
# Copy to .env.harness (gitignored) and fill in real values.
# The harness is invoked via the wrapper at:
#   test/network-harness/run-scenario.sh <scenario.yaml>
# which sources .env.harness, builds the harness binary, and runs.

# Live buyer bearer token (required for every scenario).
BUYER_TOKEN=

# SSH target for Pearl VPS (required for I1 ledger reconciliation).
# Form: user@host or a Host alias from your ~/.ssh/config.
# Examples:
#   PEARL_SSH=root@pearl-vps.malibu.tech
#   PEARL_SSH=pearl                        # if alias in ~/.ssh/config
PEARL_SSH=

# SSH target for the provider Mac to chaos-kill (required for scenarios 05, 06).
# Form: user@host or alias.
# Examples:
#   PROVIDER_SSH=ops@m1.tail-XXXX.ts.net
#   PROVIDER_SSH=m1
PROVIDER_SSH=

# OPTIONAL: override DB paths on Pearl if the deploy layout differs from
# the defaults baked into scenarios (/var/lib/macprovider-{coordinator,gateway}/*.db).
# When set, you'd need to also edit the scenario YAML to use these.
# COORDINATOR_DB_REMOTE=/var/lib/macprovider-coordinator/coordinator.db
# GATEWAY_DB_REMOTE=/var/lib/macprovider-gateway/gateway.db

# OPTIONAL: override launchd label / provider-restart command for chaos scenarios.
# Default is `launchctl kickstart -k gui/$(id -u)/live.malibu.provider`.
# Edit the scenario YAML chaos_events to substitute if needed.