.gitea/workflows/release.yaml

@@ -24,8 +24,7 @@ jobs:
           password: ${{ secrets.REGISTRY_TOKEN }}
       - name: Build and push
         run: |
-          TODAY=$(date +'%Y-%m-%d')
+          docker build -t ${REGISTRY}/${REPO_OWNER}/${IMAGE_NAME}:${{ gitea.sha }} -t ${REGISTRY}/${REPO_OWNER}/${IMAGE_NAME}:latest .
-          docker build -t ${REGISTRY}/${REPO_OWNER}/${IMAGE_NAME}:${{ TODAY }} -t ${REGISTRY}/${REPO_OWNER}/${IMAGE_NAME}:latest .
+          docker push ${REGISTRY}/${REPO_OWNER}/${IMAGE_NAME}:${{ gitea.sha }}
-          docker push ${REGISTRY}/${REPO_OWNER}/${IMAGE_NAME}:${{ TODAY }}
           docker push ${REGISTRY}/${REPO_OWNER}/${IMAGE_NAME}:latest
     

content/blog/gitea.md

@@ -1,5 +1,5 @@
 ---
-title: "Replicating Gitea Docker SSH Passthrough on K3s"
+title: "Replicating Gitea Docker SSH Passthrough on K8s"
 date: "2023-02-12"
 ---
 
@@ -21,7 +21,7 @@ Command substitution does not work in `AuthorizedKeysCommand` so I suggest creat
 
 ## Background
 
-I am currently in the process of migrating my selfhosted applications from docker-compose to Kubernetes. One of my most used selfhosted app is Gitea. I use it to host my projects, dotfiles and config files where I don't expect any contributions or I simply want to keep it more private. In my docker-compose setup I used SSH Container Passthrough from [Gitea docs](https://docs.gitea.io/en-us/install-with-docker/#SSH-container-passthrough) but when I moved Gitea to k3s I couldn't find any guides on how to achieve the same thing.
+I am currently in the process of migrating my selfhosted applications from docker-compose to Kubernetes. One of my most used selfhosted app is Gitea. I use it to host my projects, dotfiles and config files where I don't expect any contributions or I simply want to keep it more private. In my docker-compose setup I used SSH Container Passthrough from [Gitea docs](https://docs.gitea.io/en-us/install-with-docker/#SSH-container-passthrough) but when I moved Gitea to k8s I couldn't find any guides on how to achieve the same thing.
 
 I installed Gitea using the official [Helm Chart](https://gitea.com/gitea/helm-chart/). The documentation says this about enabling SSH:
 

content/blog/gitea_actions_k3s_docker.md

@@ -1,37 +0,0 @@
----
-title: "Building a Docker Container with Gitea Actions on K3s"
-date: "2023-11-25"
-draft: true
----
-
-Building a docker image and pushing it to registry with GitHub Actions is incredibily easy. Since Gitea Actions are compatible with GitHub Actions this should be easy, right?
-
-<!--more-->
-
-## Gitea Actions
-
-- Released with 1.19
-- Based of act runner
-- Mostly compatible with GitHub Actions
-
-## Building and Pushing Docker Image with GitHub Actions
-
-- straight forward with docker actions
-
-## Building with Gitea
-
-Deploying example dind-rootless
-
-Testing with the same workflow as on github
-
-docker command not found
--> switch container to callthehacker
-
-/var/run/docker.sock -> is docker daemon running?
--> Changing the DOCKER_HOST variable
-
-cant mount sys fs permission denied
--> run docker commands directly
-
-side step with buildah
-