.env.example

# Chainplot environment. Copy to .env and fill in. Never commit .env.
# Scope: this file is for developing Chainplot itself (live tests read it).
# For an analytics project, keep its own .env in the project directory —
# the CLI loads .env from the directory you run it in.
# All values stay local; tests and the CLI read them at runtime.

# --- Ingest (M2) ---------------------------------------------------------
# The live suites read RPC_URL (Ethereum mainnet, archive-capable). Postgres
# and rindexer come from compose, so there is no test database URL to set.
# Real analytics projects keep their own .env with per-chain endpoints.
RPC_URL=

# Postgres 16 for the rindexer adapter (compose.yaml provides one).
DATABASE_URL=postgresql://chainplot:chainplot@localhost:5432/chainplot

# --- Publish to S3-compatible storage (M4) -------------------------------
# The endpoint is an origin only — scheme and host, no path. For R2 that is
# https://<account-id>.r2.cloudflarestorage.com; the bucket goes in
# CHAINPLOT_S3_BUCKET. A path here is sent as the bucket name, so every file
# lands one level too deep and the public URL serves nothing.
CHAINPLOT_S3_ENDPOINT=
CHAINPLOT_S3_BUCKET=
CHAINPLOT_S3_REGION=auto
AWS_ACCESS_KEY_ID=
AWS_SECRET_ACCESS_KEY=

# --- Local overrides (optional) ------------------------------------------
# rindexer binary (default: rindexer on PATH)
# CHAINPLOT_RINDEXER_BIN=