feat(templates): Add gitea-runner docker-compose file
This commit is contained in:
@@ -1,8 +1,25 @@
|
||||
# gitea-runner (templates)
|
||||
# Gitea Actions Runner (Portainer template)
|
||||
|
||||
### Description
|
||||
Description for gitea-runner goes here.
|
||||
Gitea Actions Runner (act_runner) is a runner for Gitea Actions. It is compatible with GitHub Actions and allows you to run CI/CD workflows within your Gitea instance.
|
||||
|
||||
### Configuration
|
||||
- Path: templates/gitea-runner/docker-compose.yml
|
||||
- Status: Draft
|
||||
Quick notes:
|
||||
|
||||
- **Registration**: You will need a registration token from your Gitea instance (Site Administration > Actions > Runners).
|
||||
- **Docker-in-Docker**: To run container-based actions, the runner requires access to the Docker socket (`/var/run/docker.sock`).
|
||||
- **Persistence**: Ensure the data volume is mapped to persist the runner configuration and registration state.
|
||||
|
||||
Usage:
|
||||
|
||||
1. Import the compose file into Portainer's Stacks or App Templates.
|
||||
2. Configure the `GITEA_INSTANCE_URL` and `GITEA_RUNNER_REGISTRATION_TOKEN` environment variables.
|
||||
3. Ensure the volume mapping for `/var/run/docker.sock` is correctly set if you plan to use Docker-based workflows.
|
||||
4. Deploy the stack via Portainer.
|
||||
5. Verify the runner appears as "Online" in your Gitea settings.
|
||||
|
||||
Helpful links:
|
||||
|
||||
- Gitea Actions Documentation: https://docs.gitea.com/usage/actions/overview
|
||||
- Runner Repository: https://gitea.com/gitea/act_runner
|
||||
- Docker Hub: https://hub.docker.com/r/gitea/act_runner
|
||||
|
||||
**Status:** Ready for configuration
|
||||
|
||||
Reference in New Issue
Block a user