CI/CD

Overview This is the final piece of the Hugo publishing pipeline: a Gitea Actions workflow that automatically builds the Hugo site and deploys it straight to Cloudflare Pages every time you push to your private Gitea repo. No manual builds, no manual uploads… push to main, and the live site updates itself. Hardware / Requirements A registered and running Gitea Act Runner (see my Gitea Act Runner Setup on Proxmox guide if you haven’t set this up yet). A Cloudflare account with a Pages project already created and connected to your domain. A Cloudflare API Token with Pages edit permissions. 🌐 Prerequisite: Generate your Cloudflare API Token and Account ID beforehand (you’ll need both to authenticate the deploy step). ...

Overview Gitea ships with its own built-in CI/CD system called Gitea Actions but it needs a runner to actually execute jobs. This guide covers deploying a dedicated act_runner LXC container on Proxmox and registering it to your Gitea instance, laying the groundwork for automated Hugo builds and deploys. Hardware / Requirements Gitea already installed and running (see my Private Git Server with Gitea on Proxmox guide if you haven’t set this up yet). Admin access to your Gitea instance to enable Actions and generate a registration token. 🌐 Prerequisite: Gitea Actions is disabled by default and must be enabled in your instance’s configuration before a runner can connect to it. ...