Concepts
Concepts
What Rungar is made of and how it behaves: the ideas the guides and the reference take for granted.
From a job queued on GitHub to a machine that runs it and is deleted after.
What GitHub sees, and how many runners Rungar keeps for it.
What runners run on: a provider is one backend that creates machines, and places them itself.
Rungar keeps no state: the machines on the fleet, and their labels, are the record.
Which provider a runner goes to, what happens when one is full, and who gets the fleet when there is not enough to go round.
A runner from registration to deletion: starting, idle, busy, gone.