Files
bikoret/deploy/k8s/configmap.yaml
T
Scott KarpandClaude Fable 5.1 c0d0555aed the name: Bikoret — code, contracts, images
Headers X-Bikoret-Key / -Rebuke / -Verdict / -Bedikah; the `bikoret`
object and the "— bikoret …" fringe on a gate reply; environment
variables BIKORET_*; the image user and paths (/home/bikoret,
/tmp/bikoret, /var/lib/bikoret/manna, /etc/bikoret/secrets,
/opt/bikoret/spec); the tmp-bikoret pod volume; local databases
bikoret_dev/_test. Kubernetes resource names, the shorashim_app role and
the domain are unchanged (Tamid §1.1, "the names that still carry the
old word"). Doorpost c963c4fe…. Elixir 604/0, L3 10/0, korban 295,
Prolog bedikah 44/44. Gitea repo renamed heaviness510/bikoret (old URL
redirects).

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
2026-10-13 22:13:36 +00:00

51 lines
1.9 KiB
YAML

# Bikoret ConfigMap — non-secret configuration
# Construction spec §4.4: Tuning constants
apiVersion: v1
kind: ConfigMap
metadata:
name: shorashim-config
namespace: shorashim
data:
# L1 mount point — read-only Torah filesystem
L1_MOUNT_POINT: "/mnt/torah"
# Manna provision file location
MANNA_PROVISION_FILE: "/var/lib/bikoret/manna/today.json"
# Talmudic Engine socket
TALMUDIC_SOCKET_PATH: "/tmp/bikoret/talmudic.sock"
# Korban Processor socket — the bedikah (Construction §3.9). Opened by
# the korban-processor container, read by vav-pipeline, both over the
# shared tmp-bikoret volume. Pod-internal; never on the network.
KORBAN_SOCKET_PATH: "/tmp/bikoret/korban.sock"
# Courtyard / chatzer keys — a FILE (Construction §4.6), projected from
# the shorashim-api-keys Secret (secrets.yaml). The path is config; the
# keys never are.
API_KEYS_FILE: "/etc/bikoret/secrets/api_keys"
# The pod network. The ingress controller lives in it; only from here
# is X-Real-IP believed as the caller's address (the pe'ah's per-IP
# watch, Tamid §1.1). Nothing outside the cluster can reach the pod
# directly any more (service.yaml), so nothing outside can forge it.
TRUSTED_PROXIES: "192.168.0.0/16"
# Shoresh Engine binary — staged onto the shared shoresh-bin volume
# by the shoresh-engine-install init container (see deployment.yaml).
# vav_pipeline spawns it as an Erlang Port, i.e. as a child process of
# the vav-pipeline container, so it must be a path on THIS
# container's filesystem.
SHORESH_ENGINE_BINARY: "/opt/shoresh/shoresh-engine"
# Shabbat location — Zurich (Construction spec §4.4)
SHABBAT_LATITUDE: "47.3769"
SHABBAT_LONGITUDE: "8.5417"
SHABBAT_TIMEZONE_OFFSET: "1"
# Cycle boundary check interval (ms)
CYCLE_BOUNDARY_CHECK_INTERVAL_MS: "60000"
# Pipeline latency budget (ms) — Construction spec §2.5
PIPELINE_LATENCY_BUDGET_MS: "5000"