.env.example

# JIC — optional runtime configuration.
# Copy to .env (gitignored) and edit. Every value below is optional.

# ── Error reporting (Sentry) ─────────────────────────────────────────
# Full documentation: docs/1700-error-reporting.md
#
# Reporting is OPT-OUT: on wherever a DSN is configured, and the user turns it
# off. It is also a BUILD-time opt-in — a default image links no SDK at all and
# ignores everything below. Build a reporting-capable image with:
#
#     JIC_SENTRY=1 docker compose build
#
# JIC ships no minidumps: a memory image of this process would contain the
# user's questions and their documents. Crashes are reported as a signal name
# and a stack of addresses (sentry-native `inproc` backend), never as a dump.

# Build arg. 1 links sentry-native; 0 (the default) links nothing.
#JIC_SENTRY=0

# Enables reporting. Unset => nothing initialises and no outbound connection
# is ever made, whatever the switches below say.
#SENTRY_DSN=https://<key>@o<org>.ingest.us.sentry.io/<id>

#SENTRY_ENV=production
#SENTRY_RELEASE=
#CI_JIC_VERSION=0.3.0

# ── Kill switches ────────────────────────────────────────────────────
# These beat a DSN baked into an image, so reporting can always be turned off
# without a rebuild. Precedence: CI_LOCAL_ONLY > CI_TELEMETRY > SENTRY_DSN.

# off | false | 0 | no | disabled
#CI_TELEMETRY=off

# true | 1 | yes | on | enabled — local-only mode means zero phone-home.
#CI_LOCAL_ONLY=true

# `off` keeps handled-error reporting but installs no fatal-signal handler.
#JIC_SENTRY_CRASH_HANDLER=off

# SDK state directory. Defaults next to JIC_DB_PATH, per component. The
# containers run read_only:true, so it must land on the data volume.
#JIC_SENTRY_DB_DIR=/app/data/.sentry-ci-just-in-case-server

# ── Cloudflare Tunnel (profile: tunnel) ──────────────────────────────
# Publishes this box at https://jic.ci.computer without opening an inbound
# port. Full runbook — DNS, Access email sign-in, the monthly query cap:
# docs/1900-deployment-cloudflare.md
#
# Created in the Zero Trust dashboard (Networks → Tunnels → Create). This is a
# BEARER CREDENTIAL for the hostname: anyone holding it can run the tunnel, so
# keep it in .env (gitignored) and never in the compose file or an image.
#CLOUDFLARE_TUNNEL_TOKEN=eyJhIjoi...

# Pin the connector rather than tracking :latest, so an upstream release never
# restarts a working appliance unasked.
#CLOUDFLARED_VERSION=2026.9.1

# Host-side readiness/metrics port, bound to loopback (curl :2000/ready).
#TUNNEL_METRICS_PORT=2000

# ── Splitting the UI from the server ─────────────────────────────────
# Only needed when the web UI is served from somewhere other than this
# server — static hosting, a Pages project, or another JIC instance.
# Full guide: docs/2000-hosting-the-ui-separately.md

# Which origin may call this server's API. Required for a cross-origin UI.
# Name the ONE origin the UI is served from. Avoid "*" on a personal
# machine: with a wildcard, any page in any tab can query your JIC and read
# passages out of your documents.
#JIC_CORS_ORIGIN=https://jic.ci.computer

# The reverse direction, and only relevant when JIC itself serves the page:
# which other servers that page is allowed to call. Appended to the CSP's
# connect-src, which is 'self' by default — so pointing a JIC-served UI at a
# different backend fails as a CSP violation until this names it.
# Space-separated.
#JIC_CONNECT_SRC=https://jic.ci.computer http://localhost:8080