.env.example

# gazette configuration -- copy to .env for local dev and fill in.
# On the cloud these same names are injected as environment variables
# (OCI Vault), so the code never hardcodes any of them.
#
#   cp .env.example .env
#
# .env is gitignored; .env.example is tracked. Never commit real secrets.

# dev | prod | pytest
ENVIRONMENT=dev
LOG_LEVEL=INFO

# --- content (GitHub raw JSON) ---
GITHUB_URL=https://raw.githubusercontent.com/DynamicalSystem/content/main/
GITHUB_TOKEN=

# --- bluesky publisher ---
BLUESKY_URL=https://bsky.social
BLUESKY_USERNAME=
BLUESKY_PASSWORD=

# --- signal publisher (external Signal service over HTTP) ---
# The Signal service lives in its own repo. gazette is just an HTTP client.
# Pick the SIGNAL_URL for where gazette runs:
#
#   prod  (container on the shared signal-net):  http://signal:8080
#   dev   (gazette in a podman container, Mac):  http://host.containers.internal:8010
#   dev   (gazette run directly on the Mac host): http://127.0.0.1:8010
#
# The cloud Signal API binds to 127.0.0.1 on the box (not public), so in dev you
# reach it through an SSH tunnel:
#   ssh -i ~/.ssh/id_oci -N -L 8010:127.0.0.1:8010 ubuntu@152.67.153.4
SIGNAL_URL=http://127.0.0.1:8010
SIGNAL_IDENTITY=+447377115354

# --- state (watermarks) ---
# DATA_FOLDER + WATERMARK_FILE locate the mutable watermark JSON.
# DEV SAFETY: dev watermarks should use the `Validator` publisher (logs only) or
# target your own number. A `Signal` watermark pointed at a real group will send
# real messages from SIGNAL_IDENTITY the moment gazette runs.
DATA_FOLDER=
WATERMARK_FILE=watermarks.json