.env.example

# Compose reads these environment variables and exposes them to the container
# as Docker secrets using the `secrets:` mappings in docker-compose.yml.
# Keep these values fictitious in this example and private in your real `.env`.
CLAUDE_CODE_OAUTH_TOKEN=sk-ant-oat...
GITHUB_TOKEN=ghp_...
GIT_USER=your_username
GIT_EMAIL=your_email@example.com
# Comma-separated repositories. Each one is cloned under
# /data/workspaces/<repo-name>; spaces around commas are allowed.
# CodeDeck uses /data/workspaces as the shared root, so repositories cloned
# later by Claude and local folders created there are also available.
GIT_REPO=https://github.com/your-username/your-repo.git

# --- Relay transport (private/Haven relay, optionally over Tor) ---
# Comma-separated relay URLs. These examples are public relays known to be
# valid; replace them with relays you operate or trust as appropriate.
CODEDECK_RELAYS=wss://relay.primal.net,wss://nostr.oxtr.dev

# SOCKS5 proxy for all relay connections. It is optional and unset by default.
# Two options:
#  - Your own Tor daemon (e.g. the one already running next to your CLN
#    node): point this at wherever its SocksPort is reachable from the
#    container, e.g. socks5h://host.docker.internal:9050 (Docker Desktop) or
#    your host's LAN/bridge IP on Linux.
#  - The bundled codedeck-tor service (docker-compose.yml, `tor` profile):
#    socks5h://codedeck-tor:9050 — run `docker compose --profile tor up -d`.
# Leave unset for a direct (non-Tor) connection.
# CODEDECK_TOR_PROXY_URL=socks5h://codedeck-tor:9050

# NIP-42 AUTH (e.g. for a Haven relay) needs no configuration here — the
# bridge answers AUTH challenges with its own existing identity keypair
# (data/state.json), the same pubkey already shown as the pairing npub.
# Allowlist that pubkey in Haven's ACL; nothing else to set.