Development
Self-host act_runner on a VPS
A self-hosted runner for Gitea/Forgejo Actions.
Execute workflow jobs on your own hardware with Docker isolation, scaling from one runner to many as CI demand grows.
Why self-host act_runner?
Runners are where code actually builds; hosting your own keeps build secrets and artefacts inside your network.
How to install act_runner
- 1
Provision a VPS
Pick a Debian/Ubuntu template and get root SSH in about a minute.
- 2
Install the runtime
Install Docker + act_runner.
- 3
Deploy the application
Net what you need from the project’s official source and run it.
- 4
Put it behind TLS
Reverse-proxy with Nginx and issue a Let’s Encrypt certificate.
- 5
Add it to your backups
Include the data directory and database in your backup routine before you rely on it.
Practical tips
- Give act_runner its own database user with rights only on its own schema.
- Reverse-proxy act_runner and terminate TLS at the proxy so certificates are managed in one place.
- Take a VPS snapshot before major upgrades so you can roll back cleanly.
- Keep act_runner patched — most self-hosting incidents are unpatched software.
Frequently asked questions
- How much RAM does act_runner need?
- Plan on 2–4 GB for typical use; add headroom if you expect many concurrent users.
- What stack does act_runner run on?
- Docker + act_runner.
- Can I run other things on the same VPS?
- Yes — size the plan so act_runner plus your other workloads fit in RAM with room to spare.
Looking for something else? Popular alternatives include Drone runner, Woodpecker agent, GitLab runner — browse all app guides.