From 80d986c0465b060a7e3dac3060c77ec256088b28 Mon Sep 17 00:00:00 2001 From: Mikael Hugo Date: Sun, 17 May 2026 23:12:35 +0200 Subject: [PATCH] ci: default sf-server image to Forgejo registry --- .forgejo/workflows/self-deploy.yml | 4 ++-- docs/specs/sf-self-deploy.md | 6 ++++-- 2 files changed, 6 insertions(+), 4 deletions(-) diff --git a/.forgejo/workflows/self-deploy.yml b/.forgejo/workflows/self-deploy.yml index b6b400eb4..adee9c9c0 100644 --- a/.forgejo/workflows/self-deploy.yml +++ b/.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 }}" \ . diff --git a/docs/specs/sf-self-deploy.md b/docs/specs/sf-self-deploy.md index 519c0926b..d47072c6d 100644 --- a/docs/specs/sf-self-deploy.md +++ b/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