Forgejo is a Git forge you host yourself: repositories, users, SSH access and, with Forgejo Actions, CI/CD on your own runners. Codeberg runs on it. I run it as a rootless Podman container on my VPS and deploy with a Forgejo Actions runner on the same machine.
What matters in practice
- Image: the rootless image
codeberg.org/forgejo/forgejo:<major>-rootlesscomes from Codeberg, not from Docker Hub. - Configuration:
custom/conf/app.iniin the data volume. Actions stay off until[actions] ENABLED = true. - Actions:
DEFAULT_ACTIONS_URL = https://code.forgejo.orgpointsuses:to Forgejo's mirrors of common actions such asactions/checkout. - SSH: the built-in SSH server listens on a port of its own (2222 in my setup), next to the system's SSH on 22.
- Resources: about 130 to 145 MB of RAM in operation.
- Used in
-
- Astro Client Islands under a Strict CSP Why Astro islands fail silently under script-src 'self', how I allowed the two hydration inlines by sha256 hash, and a deploy check for hash drift.
- Forgejo on Debian 13 with Rootless Podman Forgejo as a rootless Podman container under its own user: a Quadlet for systemd, Caddy in front, SSH on port 2222 and the problems I ran into.
- Setting Up a Forgejo Actions Runner Push-to-deploy with a self-hosted Forgejo Actions runner on the same VPS: own user, no Docker, narrow sudo rights and secrets kept in Forgejo.
- Tags