ci: default sf-server image to Forgejo registry

.forgejo/workflows/self-deploy.yml

@@ -62,7 +62,7 @@ jobs:
         shell: bash
         run: |
           set -euo pipefail
-          repo="${SF_IMAGE_REPOSITORY:-${SF_REGISTRY:-registry.centralcloud.com}/singularity/sf-server}"
+          repo="${SF_IMAGE_REPOSITORY:-${SF_REGISTRY:-registry.infra.centralcloud.com}/singularity/sf-server}"
           tag="${GITHUB_SHA:-${CI_COMMIT_SHA:-$(git rev-parse HEAD)}}"
           echo "image=${repo}:${tag}" >> "$GITHUB_OUTPUT"
           echo "SF_RELEASE_IMAGE=${repo}:${tag}" >> "$GITHUB_ENV"
@@ -83,7 +83,7 @@ jobs:
             --build-arg "SF_GIT_SHA=${GITHUB_SHA:-$(git rev-parse HEAD)}" \
             --build-arg "SF_GIT_REF=${GITHUB_REF_NAME:-$(git rev-parse --abbrev-ref HEAD)}" \
             --build-arg "SF_RELEASE_IMAGE=${{ steps.image.outputs.image }}" \
-            --build-arg "SF_IMAGE_REPOSITORY=${SF_IMAGE_REPOSITORY:-${SF_REGISTRY:-registry.centralcloud.com}/singularity/sf-server}" \
+            --build-arg "SF_IMAGE_REPOSITORY=${SF_IMAGE_REPOSITORY:-${SF_REGISTRY:-registry.infra.centralcloud.com}/singularity/sf-server}" \
             -t "${{ steps.image.outputs.image }}" \
             .
 

docs/specs/sf-self-deploy.md

@@ -30,8 +30,10 @@ The required gates are:
 - build `docker/Dockerfile.sf-server`
 - generate `dist/sf-release-manifest.json`
 
-The image builder is Docker/BuildKit. The deployment contract starts at the OCI
-image plus release manifest.
+The image builder is Docker/BuildKit. The default Forgejo image repository is
+`registry.infra.centralcloud.com/singularity/sf-server`, matching the in-cluster
+registry host already used by GitOps workloads. The deployment contract starts
+at the OCI image plus release manifest.
 
 ## Server Runtime