Introduction
Introduction
Rungar runs GitHub Actions runners, a fresh machine for every job, on hosts of your own and in the cloud.
It keeps a GitHub runner scale set supplied with runners: each is a machine
created for one job and deleted after it, so nothing is shared between two
jobs. The daemon, rungar, learns from GitHub how many jobs are waiting and
creates that many runners through its providers – Dicer hosts,
Proxmox VE, Google Cloud and AWS – and the rungar command line shows and
steers what it is doing.
Install Rungar, point it at GitHub and a Dicer host, and run a first job on a VM of its own.
How Rungar turns GitHub’s jobs into machines, and what it can be relied on for.
How to do one thing well, step by step.
Where runners run: Dicer hosts, Proxmox VE, GCP and AWS.
Whole configurations to start from and adapt.
The configuration, the command line, the metrics, the events and the labels, in full.