wip: ci

.gitea/workflows/build.yml

@@ -18,6 +18,6 @@ jobs:
         with:
           registry: git.gtz.dk
           username: ${{ gitea.actor }}
-          password: ${{ secrets.CI_TOKEN }}
+          password: ${{ secrets.GITEA_TOKEN }}
       - name: push container
         run: docker push git.gtz.dk/${{ gitea.repository }}:latest

content/posts/how-to-blog.md

@@ -123,16 +123,18 @@ I also have other projects that I host on my VPS (Virtual Private Server) such m
 
 ## Continuous Integration
 I am using my personal [gitea instance](https://git.gtz.dk/agj/blog) to host the source code for this blog - which means that I will be using the integrated CI system there, but you can use whichever CI service you'd like.
-The general concepts of the workflow should be fairly easy to translate to any kind of CI
-
-<!-- TODO: Implement the fucking thing -->
-
-This setup also gives us the possibility of performing traditional code-review before releasing by using [pull requests]().
-This should empower us to identify and correct issues (e.g. spelling mistakes or whatever) before they are pushed to the official website.
+The general concepts of the workflow should be fairly easy to translate to any kind of CI, but this is how my setup looks like:
 
 ```yaml
 ```
 
+Make sure to replace the `git.gtz.dk` website mentions with your own github hosting service (whether self-hosted, or `github.com`).
+Note that the syntax is extemely similar to GitHub Actions - in fact Gitea Actions are trying to be 1 to 1 compatible with GitHub Actions, so it should be relatively straight forward.
+
+This setup also gives us the possibility of performing traditional code-review before releasing by using [pull requests](https://docs.gitea.com/next/usage/pull-request?_highlight).
+This should empower us to identify and correct issues (e.g. spelling mistakes or whatever) before they are pushed to the official website.
+
+
 ## Continuous Delivery
 With a docker image readily available