Training
Running Forgejo in production Pilot
Move off GitHub without losing your CI
A course about moving off GitHub onto Forgejo and running the result: the migration itself, Actions and runners, backup, restore, upgrades and SSO, scaling and cost, and the real migration for a whole organisation.
Pre-registering is an email to me, nothing more. I write back when the first sessions are scheduled. No newsletter.
At a glance
- Who it is for
- Teams on GitHub with a reason to move (cost, sovereignty, a platform decision already made), and teams already self-hosting Forgejo who have not yet done backup, SSO or a capacity plan.
- Who it is not for
- Teams with no reason to move anything, and teams who want Forgejo run for them.
- Format
- 9 self-paced workshops in a hosted browser lab. No cohort, no fixed dates.
- Where the work happens
- A browser workspace (Educates) with two Forgejo instances of your own — one standing in for GitHub, one you migrate into — and a project in the course cloud for the workshops that need runners.
- Stack
- Forgejo 15 with Actions, forgejo-runner 13.2, forgejo-fleet v0.1.0, a live mockup of the Hetzner Cloud API.
- You bring
- A browser.
- You walk out with
- From workshop 1: a repository migrated with issues, labels, milestones and CI workflow, the workflow running green, and the one-line difference for doing the same against real GitHub. The other eight add a sized runner pool, a rehearsed backup, restore and upgrade, SSO/LDAP and object storage, a cost model, a cutover plan, and more.
- Price
- Free during the pilot, limited seats.
Workshops#
- The migration dry run
- Actions and runners
- Operating it — backup, restore, upgrades, SSO/LDAP, object storage
- Scaling and cost
- The real migration — large repositories, LFS, users, permissions, mirroring
- A coding agent in CI, on your own infrastructure
- The private monorepo with public parts
- Surviving the open internet — bots, scrapers and abuse
- Scheduled work — dependency updates, scanning and SBOMs