Files
psyc/.env.example
m17hr1l 92f754e012 stage-28: wire LETSENCRYPT_HOST + LETSENCRYPT_EMAIL on the cockpit service
Adds the two env vars nginxproxy/acme-companion looks for to issue +
auto-renew the TLS cert for psyc.neuronetz.ai. LETSENCRYPT_EMAIL is
interpolated from the prod .env (LETSENCRYPT_EMAIL=...) with a sensible
fallback so dev / local deploys don't fail on the variable being unset.
.env.example documents the var.

Requires the proxy stack to (a) have acme-companion alongside
nginx-proxy with shared certs/vhost.d/html volumes and (b) publish :443.
psyc-side change only — no app code touched.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
2026-05-25 16:42:46 +02:00

27 lines
1.1 KiB
Plaintext

# psyc — per-developer secrets. Copy to `.env` (already gitignored) and fill in.
#
# cp .env.example .env
# # edit .env with your own keys
#
# Do not commit .env. Each developer keeps their own keys local.
# --- CTI source API keys (sources we may add to Scoutline) ---
# ThreatFox / abuse.ch — free auth key at https://auth.abuse.ch/
THREATFOX_AUTH_KEY=
# AlienVault OTX — free key at https://otx.alienvault.com/api
OTX_API_KEY=
# NIST NVD — free key at https://nvd.nist.gov/developers/request-an-api-key
# (raises throttling from ~5 to ~50 requests / 30s)
NVD_API_KEY=
# --- Production-only: Let's Encrypt email for the acme-companion sidecar ---
# Used as the contact address for the TLS cert acme-companion issues for
# psyc.neuronetz.ai. Safe to leave the default in dev (cert isn't issued
# without a reachable acme-companion + public DNS + :443).
# LETSENCRYPT_EMAIL=admin@neuronetz.ai
# --- Internal service URLs — overridden in docker compose; defaults for venv CLI ---
# PSYC_MOCK_CERT_URL=http://127.0.0.1:8770
# PSYC_INFERENCE_URL=http://127.0.0.1:8771
# PSYC_DATA_DIR=./data