arechen/EapilSkillMarket
1
1
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Document Docker Gitea sync runner requirements

Browse Source 
Constraint: Docker-hosted Gitea only executes scheduled workflows when Actions and act_runner are configured.

Rejected: Assuming .gitea/workflows runs by itself | A Gitea runner is required to poll and execute jobs.

Confidence: high

Scope-risk: narrow

Directive: Keep runner prerequisites documented when changing the sync workflow shell or runtime dependencies.

Tested: python scripts\\validate_marketplace.py.

Not-tested: Gitea act_runner execution on the remote Docker host.
This commit is contained in:
AreChen
2026-06-10 15:40:36 +08:00
parent 843b4e23c4
commit 9342863eba
1 changed files with 8 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
README.md
+8
View File
@@ -99,6 +99,14 @@ python scripts\validate_marketplace.py
`.gitea/workflows/sync-external-skills.yml` is a scheduled workflow prototype for Git-side periodic sync. `.gitea/workflows/sync-external-skills.yml` is a scheduled workflow prototype for Git-side periodic sync.
For a Docker-hosted Gitea instance, the workflow file alone is not enough. Gitea must have Actions enabled and an `act_runner` container registered before scheduled jobs will run. The runner that handles this repository should provide:
- A label matching `runs-on: ubuntu-latest`, or adjust the workflow to your runner label.
- `git`, `python`, and `pwsh` in the job environment.
- Network access from the job container to GitHub for upstream skill repos and to the Gitea instance for checkout/push.
If the Gitea server does not have Actions enabled, run the same sync command from a host cron job or a small maintenance container that checks out this repository, runs the sync script, validates, commits, and pushes changes.
## Layout ## Layout
```text ```text