coulomb/railiance-apps
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Deploy Forgejo on railiance01 using gitea-charts/gitea 12.5.0

Browse source 
Pin chart to 12.5.0 because 12.6+ calls `gitea config edit-ini`, which
Forgejo 11 lacks. Ingress targets forgejo-gitea-http (Helm release naming).
Smoke test uses GET for /v2/ registry challenge (HEAD returns 405).
This commit is contained in:
tegwick 2026-07-03 21:28:32 +02:00
parent 6d00232865
commit 75698636c6
8 changed files with 296 additions and 2 deletions
Download patch file Download diff file Expand all files Collapse all files

9
tools/forgejo-smoke.sh Executable file
View file

@ -0,0 +1,9 @@
#!/usr/bin/env bash
set -euo pipefail
BASE_URL="${FORGEJO_BASE_URL:-https://forgejo.coulomb.social}"
curl -fsS "${BASE_URL}/" -o /dev/null -w "root_http=%{http_code}\n"
# HEAD returns 405 on Forgejo/Gitea; GET returns 401 + Docker-Distribution-Api-Version.
curl -sSI -X GET "${BASE_URL}/v2/" | awk 'BEGIN{code=""; ok=0} /^HTTP/{code=$2} /^[Dd]ocker-[Dd]istribution-[Aa]pi-[Vv]ersion:/{ok=1; print "registry_challenge=ok"} END{if (code=="" || !ok) exit 1; if (code!="401" && code!="200") {print "registry_http=" code; exit 1} else {print "registry_http=" code}}'
echo "forgejo smoke ok: ${BASE_URL}"