35 lines
1.5 KiB
Markdown
35 lines
1.5 KiB
Markdown
# Gitea Actions demo
|
|
|
|
A minimal repository that runs a Gitea Actions workflow on the in-cluster runner.
|
|
|
|
## Prerequisites
|
|
|
|
- Gitea deployed and reachable (VPN required): `https://gitea.stg.dadosfera.ai`
|
|
- The act_runner registered and **Idle** (Site Administration → Actions → Runners) — see the root README runbook.
|
|
|
|
## Walkthrough
|
|
|
|
1. Log in at `https://gitea.stg.dadosfera.ai` with the admin credentials from AWS Secrets Manager (`stg/gitea/admin`).
|
|
|
|
2. Create a repository, e.g. `demo` (under your user or a new org). Leave "Initialize repository" unchecked.
|
|
|
|
3. Push this directory's content to it (HTTPS only — SSH is disabled on this instance):
|
|
|
|
```bash
|
|
cd examples/demo-repo
|
|
git init -b main
|
|
git add .
|
|
git commit -m "demo"
|
|
git remote add gitea https://gitea.stg.dadosfera.ai/<owner>/demo.git
|
|
git push gitea main
|
|
# authenticate with the admin username + password, or an application token
|
|
# (Settings → Applications → Generate New Token)
|
|
```
|
|
|
|
4. Open the repo's **Actions** tab in Gitea. The `Demo` workflow should be running; it checks out the code, prints system info, and runs `app.py`. Green check = the PoC loop is closed.
|
|
|
|
## How it resolves
|
|
|
|
- `runs-on: ubuntu-latest` maps to the runner label `ubuntu-latest:docker://gitea/runner-images:ubuntu-latest` — the job runs in that image inside the runner pod's docker-in-docker sidecar.
|
|
- `actions/checkout@v4` is fetched from GitHub because the instance sets `DEFAULT_ACTIONS_URL: github` (cluster nodes need outbound internet).
|