Self-Hosted CI With No Per-Minute Bill (Forgejo)

Your own Forgejo runners, your own container registry, and a deploy step that actually reaches your services. Same YAML you already know, no per-minute billing. This is episode 2 of Self-Hosted Company OS. In episode 1 we deployed the whole stack on one €15 server; here we turn Forgejo into a real GitHub replacement with CI: runner registration the offline way, a Docker sandbox that does not hand your server to anyone who can push a branch, Forgejo's built-in container registry, and a locked-down deploy job. Compose file, runner config and the workflow (free, no signup): https://git.selfhostedops.com/selfhostedops/selfhostedops-stack Chapters: 00:00 A push that builds, ships and deploys itself 00:34 Why the half-move to self-hosted git breaks 02:01 The four pieces 03:07 Bumping Forgejo, and why you pin majors 03:55 Turning Actions on (the line everyone misses) 04:30 Registering the runner without the web token trap 05:23 The Docker sandbox, and the shortcut that owns your server 06:24 Labels, or why your job sits in "waiting" forever 07:49 The first workflow 08:40 Build, push to your own registry, deploy 10:11 Real costs, honest math 11:47 What is next Episode 1 (the stack this builds on): https://youtu.be/1s0DvJklYAE Channel site: https://selfhostedops.com Subscribe: https://youtube.com/@selfhostedops Tools shown: Forgejo, Forgejo Actions, forgejo-runner, Docker-in-Docker, Docker Compose, Caddy. Disclosure: this video uses a synthetic (AI) voiceover. #selfhosted #cicd #forgejo #docker #devops