3
Configuring forgejo actions
blogops.mixinet.netLast week I decided I wanted to try out forgejo actions to build this blog instead of using
webhooks, so I looked the documentation and started playing with it until I had it working as I wanted.
This post is to describe how I’ve installed and configured a forgejo runner, how I’ve added an
oci organization to my instance to build, publish and mirror container images and added a couple of
additional organizations (actions and docker for now) to mirror interesting
actions.
The changes made to build the site using actions will be documented on a separate post, as I’ll be using this entry to
test the new setup on the blog project.
Installing the runnerThe first thing I’ve done is to install a runner on my server, I decided to use the
OCI image installation method, as it seemed to be the easiest and fastest
one.
The commands I’ve used to setup the runner are the following:
$ cd /srv
$ git clone https://forgejo.mixinet.net/blogops/forgejo-runner.git
$ cd forgejo-runner
$ sh ./bin/setup-runner.sh
Sisi mucho ojito con forgejo con el tema automatización CI/CD que así podemos dejar más fácilmente de depender de github y gitlab
Tal cual.
Aunque el sistema de CI/CD de Forgejo es un clon del de Github Actions y a mí no me guste 😅