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>
This commit is contained in:
Scott KarpandClaude Fable 5.1 committed 2026-10-13 22:13:36 +00:00
1 parent 017a9b89d4
commit c0d0555aed
46 files changed
+189 -189

No files matched your search

+3 -3
View File
@@ -1,13 +1,13 @@
# L3 tests require PostgreSQL — excluded by default
# Run with: SHORASHIM_L3=1 mix test --include l3
# Run with: BIKORET_L3=1 mix test --include l3
ExUnit.start(exclude: [:l3])
# The manna ledger resumes a day it finds on disk (ledger.json). A run
# that was interrupted could leave one behind; no test should inherit it.
if Process.whereis(VavPipeline.MannaLedger), do: VavPipeline.MannaLedger.reset()
if System.get_env("SHORASHIM_L3") do
# The application already starts the Repo when SHORASHIM_L3 is set
if System.get_env("BIKORET_L3") do
# The application already starts the Repo when BIKORET_L3 is set
# (Application.maybe_add_repo); starting it again here was a MatchError
# on {:error, {:already_started, _}} and no L3 test could run.
case VavPipeline.Repo.start_link() do