lunny/helm-chart
1
0
Fork 0
Code Issues 36 Pull Requests 14 Actions Packages Projects Releases 93 Wiki Activity

rebased: Add Gitea Actions act runner #666

Merged
vjm merged 27 commits from gitea-actions into main 2024-11-10 13:35:57 +00:00
Conversation 27 Commits 27 Files Changed 24 +3 -14
1 changed files with 3 additions and 14 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files
Showing only changes of commit 1d52aca44d - Show all commits

17
readme-actions-dev.md
View File

@ -1,19 +1,8 @@
# Gitea Actions # Gitea Actions
In order to use the Gitea Actions act-runner you must: In order to use the Gitea Actions act-runner you must either:
- set the following environment variables to `deployment.env` (modify LOCAL_ROOT_URL if you used a different service name):
```yaml
deployment:
env:
- name: GITEA__ACTIONS__ENABLED
value: 'true'
- name: GITEA__SERVER__LOCAL_ROOT_URL
value: http://gitea-http:3000
```
- enable persistence (used for automatic deployment to be able to store the token in a place accessible for the Job) - enable persistence (used for automatic deployment to be able to store the token in a place accessible for the Job)
- create a secret containing the act runner token and reference it as a `existingSecret`
In order to use Gitea Actions, you must log on the server that's running Gitea and run the command: In order to use Gitea Actions, you must log on the server that's running Gitea and run the command:
`gitea actions generate-runner-token` `gitea actions generate-runner-token`
@ -37,7 +26,7 @@ the command `gitea actions generate-runner-token`. After generating the token, y
```yaml ```yaml
actions: actions:
job: provisioning:
enabled: false enabled: false
existingSecret: "secret-name" existingSecret: "secret-name"
existingSecretKey: "secret-key" existingSecretKey: "secret-key"