Forgejo Runner

Install

LXC container VM (ready-made image)

bash -c "$(curl -fsSL https://iac.heyer.systems/forgejo-runner/ct.sh)"

bash -c "$(curl -fsSL https://iac.heyer.systems/forgejo-runner/vm.sh)"

Then: No web UI – the runner appears in Forgejo under Settings → Actions → Runners. Not registered yet? Set forgejo_runner_url, forgejo_runner_uuid and forgejo_runner_token in /etc/iac/settings.env, then run update.

Settings per instance

When creating a container, as var_<setting>:

var_forgejo_runner_url="<value>" bash -c "$(curl -fsSL https://iac.heyer.systems/forgejo-runner/ct.sh)"

Set or change later, in the guest (for VMs the only way so far): a line forgejo_runner_url=<value> in /etc/iac/settings.env – no quotes, the last line of a setting wins – then:

update

Missing or empty = the app's default. Do not edit the configuration files iac writes – update overwrites them; their first lines name the file for local changes.

Update

In the guest:

update

Debian packages, Forgejo Runner, modules and the iac configuration. Major versions never change automatically.

Add modules – any time, in containers and VMs alike:

update --list-modules
update --add-modules node-exporter

All modules · More about update

Adopt an existing installation in the guest as root

bash -c "$(curl -fsSL https://iac.heyer.systems/forgejo-runner/adopt.sh)"

Checks first and stops before any change if an automatic adoption is not possible – then follow the migration guide.