Microblog 13


Yesterday I played the “what’s the most complex way to deploy my static website?” game.

This is what I got: when I push my hugo website’s code to #forgejo, #WoodpeckerCI picks it up and if there’s a new build version (stored in a file), it creates a matching tag in git. A different workflow picks up the tag and builds a container and pushes it back to forgejo (which acts as a container registry too).

When #FluxCD picks up the new image version, it updates the kubernetes deployment in the giterepo, and when these changes get synced by flux, the new image gets deployed into the #k3s cluster.

All #SelfHosted!