counterweight/personal_infra
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
personal_infra/ansible/services/forgejo-runner/SETUP.md
counterweight 8a3fddbe49
docs: mark Uptime Kuma as decommissioned 
README, both setup guides and the forgejo-runner notes now point at
archive/uptime_kuma/ instead of describing a live service.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
2026-09-11 22:43:56 +02:00

975 B
Raw Blame History

Forgejo Runner Setup

Obtaining the Registration Token

  1. Log in to the Forgejo instance at https://forgejo.contrapeso.xyz
  2. Go to Site Administration > Actions > Runners
  3. Click Create new runner
  4. Copy the registration token

Configuring the Token

Paste the token into ansible/infra_secrets.yml:

forgejo_runner_registration_token: "YOUR_TOKEN_HERE"

Running the Playbook

ansible-playbook ansible/services/forgejo-runner/deploy_forgejo_runner_playbook.yml

Verifying

  1. On the VM: systemctl status forgejo-runner should show active
  2. In Forgejo: Site Administration > Actions > Runners should show the runner as online
  3. In Uptime Kuma: the forgejo-runner-healthcheck push monitor should be receiving pings (Uptime Kuma was decommissioned 2026-09-11 — this check no longer applies. The healthcheck timer still runs on the host but pushes nowhere. See archive/uptime_kuma/.)