From 174216f998cf5be4dbb85e98f2df7ad88ac444c1 Mon Sep 17 00:00:00 2001 From: Asger Gitz-Johansen Date: Mon, 2 Dec 2024 13:18:55 +0100 Subject: [PATCH] wip: ci --- .gitea/workflows/build.yml | 3 ++- content/posts/how-to-blog.md | 14 ++++++++------ 2 files changed, 10 insertions(+), 7 deletions(-) diff --git a/.gitea/workflows/build.yml b/.gitea/workflows/build.yml index 770e31a..a6ad136 100644 --- a/.gitea/workflows/build.yml +++ b/.gitea/workflows/build.yml @@ -16,8 +16,9 @@ jobs: - name: login uses: docker/login-action@v3 with: + # NOTE: See https://gitea.com/gitea/docs/pulls/77/files registry: git.gtz.dk username: ${{ gitea.actor }} - password: ${{ secrets.CI_TOKEN }} + password: ${{ secrets.PACKAGE_TOKEN }} - name: push container run: docker push git.gtz.dk/${{ gitea.repository }}:latest diff --git a/content/posts/how-to-blog.md b/content/posts/how-to-blog.md index daf05dc..8e0f03f 100644 --- a/content/posts/how-to-blog.md +++ b/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 - - - -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`) and replace the `gitea/GITEA` mentions with `github/GITHUB` instead. +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