Scott KarpandClaude Fable 5.1
354e223384
From a reading of the gate's documents (2026-10-21): - AGENTS.md: Steps 14 and 15 shown Pending while the Port and both sockets have carried live traffic since the gate was built → Done, with what carries them; "next build task" now points at the open items, the phase tables being complete. - README.md: the repository tree omitted azazel_processor, kushya_generator, mesorah, src/tools and scripts → listed, each in a line. - deploy/ARCHITECTURE.md: the judgment path holds no model, said in writing — the examination is Python patterns and Prolog rules, the judges consult that Prolog; kushya_generator (a fine-tuned model in this repo, not deployed, not wired) is an OFFERER whose output is examined, never a component the bedikah, the engine or a judge consults. The kohen is not the offerer. azazel_processor listed. - The map: the repository is public; eleven files named the ingress NLB's literal address and five the kohen's kubeconfig path. Docs now use the domains (git.bikoret.ch, bikoret.ch) or "<NLB-IP>" with the kubectl query that answers it; the kubeconfig is "$KUBECONFIG" / "$HOME/.kube/<your-cluster>.yaml". gitea-public-apply.sh takes NLB from the environment. None of it was a secret; all of it was a map. - OTP pin: checked, not changed — the segfault in the build log was a source-built OTP 26.2.1 on macOS; the image is hexpm's 26.2.1 with ERL_FLAGS +JMsingle. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
33 lines
1.5 KiB
YAML
33 lines
1.5 KiB
YAML
# Strategic-merge patch for the Gitea Deployment (namespace temple-council,
|
|
# which is NOT otherwise managed from this repo): make Gitea's own URL the
|
|
# public HTTPS host, so its OAuth2 authorize/token endpoints and the
|
|
# issuer in /.well-known/openid-configuration are reachable by claude.ai.
|
|
#
|
|
# kubectl -n temple-council patch deploy gitea --patch-file deploy/k8s/gitea-public-patch.yaml
|
|
#
|
|
# The Gitea image rewrites app.ini from GITEA__section__KEY at start, so
|
|
# this replaces ROOT_URL/DOMAIN (were http://gitea.temple-council.ch, a
|
|
# name that never resolved) and SSH_DOMAIN (was 185.19.29.94, an NLB IP
|
|
# released on 2026-10-06). Clone URLs shown by Gitea become
|
|
# https://git.bikoret.ch/... and git@git.bikoret.ch:...; the old
|
|
# http://<NLB-IP>:3000 remote keeps working for push/pull.
|
|
# Side effect: with an https ROOT_URL Gitea marks its session cookie
|
|
# Secure, so the WEB UI must be used at https://git.bikoret.ch, not on
|
|
# the plain-HTTP :3000 door (git over :3000 is unaffected).
|
|
spec:
|
|
template:
|
|
spec:
|
|
containers:
|
|
- name: gitea
|
|
env:
|
|
- name: GITEA__server__ROOT_URL
|
|
value: "https://git.bikoret.ch/"
|
|
- name: GITEA__server__DOMAIN
|
|
value: "git.bikoret.ch"
|
|
- name: GITEA__server__SSH_DOMAIN
|
|
value: "git.bikoret.ch"
|
|
# [DEFAULT] APP_NAME — the title and brand on every Gitea page.
|
|
# Was "Shorashim"; the system is named Bikoret (PRD §0).
|
|
- name: GITEA____APP_NAME
|
|
value: "Bikoret"
|