Remove temporary Netbird connectivity debug step

The deploy pipeline works end-to-end now (Gimli deploys successfully),
so the diagnostic step used to trace the WireGuard/TUN issue is no
longer needed. RPIC continue-on-error is kept until the cluster returns.

.github/workflows/build-docker-images.yml

@@ -46,8 +46,11 @@ jobs:
           tags: |
             ${{ env.REGISTRY }}/${{ gitea.repository_owner }}/blog-ahmza-com:latest
             ${{ env.REGISTRY }}/${{ gitea.repository_owner }}/blog-ahmza-com:${{ gitea.event.head_commit.id }}
-          cache-from: type=gha
-          cache-to: type=gha,mode=max
+          # Registry-backed build cache. The GitHub-hosted 'gha' cache is not
+          # reachable from self-hosted Gitea runners, so store the cache as a
+          # dedicated tag in the same registry instead.
+          cache-from: type=registry,ref=${{ env.REGISTRY }}/${{ gitea.repository_owner }}/blog-ahmza-com:buildcache
+          cache-to: type=registry,ref=${{ env.REGISTRY }}/${{ gitea.repository_owner }}/blog-ahmza-com:buildcache,mode=max
   deploy:
     runs-on: ubuntu-latest
     needs: build
@@ -58,9 +61,13 @@ jobs:
         with:
           setup-key: ${{ secrets.NETBIRD_SETUP_KEY }}
           hostname: 'gitea-actions-blog'
-          management-url: 'https://netbird.ahmza.com'
+          management-url: ${{ secrets.NETBIRD_URL }}
 
       - name: Deploy to RPIC-Cluster
+        # RPIC cluster is temporarily out of service. Don't let its failure
+        # block the Gimli deploy or fail the whole job. Remove this line once
+        # the cluster is back.
+        continue-on-error: true
         uses: appleboy/ssh-action@v1
         with:
           host: ${{ secrets.RPIC_HOST }}

README.md

@@ -4,10 +4,10 @@
 This repository contains the source code for my personal blog hosted at [blog.ahmza.com](https://blog.ahmza.com).
 
 ## Features
-Using GitLab provides several advantages:
-- **Highly Customizable CI/CD Pipelines**: Automated processes for building and deploying the blog.
-- **GitLab Container Image Repository**: Efficient management and storage of container images.
-- **Custom GitLab Runners**: Flexibility in managing the CI/CD environment.
+Using Gitea provides several advantages:
+- **Highly Customizable CI/CD Pipelines**: Automated processes for building and deploying the blog via Gitea Actions.
+- **Gitea Container Image Repository**: Efficient management and storage of container images.
+- **Custom Gitea Runners**: Flexibility in managing the CI/CD environment.
 
 The CI/CD pipeline is configured to build the blog for both amd64 and arm64
 architectures, allowing me to host the site on my [Pi cluster](https://blog.ahmza.com/posts/pi-docker-swarm/)
@@ -33,7 +33,7 @@ sacrificing performance.
 
 ## Implementation
 - **Hugo**: Converts Markdown files into static HTML/CSS/JS files.
-- **GitLab CI/CD**: Automates the build process and creates Docker images.
+- **Gitea Actions**: Automates the build process and creates Docker images.
 - **Kubernetes Cluster**: Serves the static files to users.
 
 ## To-Do List
@@ -47,7 +47,8 @@ sacrificing performance.
 ## Notes
 
 ### Cloning the Repository
-To clone this repository along with its submodules, use the following command:
+The Blowfish theme is managed as a Hugo module, so no submodules are required.
+Clone the repository with:
 ```bash
-git clone git@gitlab.com:ahmza/blog.git
+git clone ssh://gitea@tea.ahmza.com:2222/ahmza/blog-ahmza-com.git
 ```

compose.yml

@@ -1,6 +1,6 @@
 services:
   blog:
-    image: ghcr.io/ahmzaa/blog-ahmza-com
+    image: tea.ahmza.com/ahmza/blog-ahmza-com:latest
     ports:
       - 80:80
     restart: unless-stopped