- service.yaml: the shorashim.ch host rule is gone from the Ingress; the no-host catch-all stays for http://185.19.28.170 - gitea-public-patch.yaml: APP_NAME "Shorashim" → "Bikoret" (title and brand on every Gitea page) - shorashim-ch-takedown.sh: the operator's apply (ingress, orphan mcp.shorashim.ch TLS secret, Gitea patch + rollout) with verification - KOHEN.md, AGENTS.md: examples and the endpoint table use bikoret.ch 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://185.19.28.170: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"
|