29 lines
792 B
Markdown
29 lines
792 B
Markdown
|
# 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`:
|
||
|
|
|
||
|
|
```yaml
|
||
|
|
forgejo_runner_registration_token: "YOUR_TOKEN_HERE"
|
||
|
|
```
|
||
|
|
|
||
|
|
## Running the Playbook
|
||
|
|
|
||
|
|
```bash
|
||
|
|
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
|