# Gitea Runner Setup

Two self-hosted runners for the Gitea instance at `http://143.244.157.110:3000`.

## Linux Runner (`talkedit-builder`)

- **Host**: this machine (CachyOS)
- **Binary**: `~/.local/bin/gitea-runner`
- **Config**: `~/.runner`
- **Labels**: `ubuntu-latest` → `docker://node:22-bookworm`, `ubuntu-24.04` → `docker://node:22-bookworm`
- **Executor**: Docker
- **Service**: user systemd unit `talkedit-runner.service`

### View runner daemon logs

```bash
journalctl --user -u talkedit-runner --no-pager -n 100
# or follow live:
journalctl --user -u talkedit-runner -f
```

### Restart

```bash
systemctl --user restart talkedit-runner
```

### Workflow job logs (step output)

Not stored locally — streamed to the Gitea server. Download from the Actions UI:
`http://143.244.157.110:3000/dillon_stuff/TalkEdit/actions/runs/<run_id>`

---

## Windows Runner (`windows-laptop`)

- **Host**: Windows laptop
- **Binary**: `%USERPROFILE%\gitea-runner-windows-amd64.exe`
- **Labels**: `windows-latest`
- **Executor**: host (runs directly, no Docker)

### Runner daemon logs

| Mode | Logs |
|---|---|
| Foreground (`daemon`) | PowerShell console stdout |
| Windows service | `%ProgramData%\gitea-runner\log\` or Event Viewer |

### Workflow job logs

Same as Linux — download from Gitea Actions UI.

---

## Why Rust/Python jobs fail

The Linux runner maps `ubuntu-latest` to `docker://node:22-bookworm` which only has Node.js. The Rust and Python steps try to install toolchains (`dtolnay/rust-toolchain`, `actions/setup-python`) inside the Docker container, but something is failing early.

**To debug**: download the full log from Gitea Actions UI and look for the first `error` or `FAILED` line after the initial setup steps — the snippets pasted so far only show the tail (cleanup/post steps).