---
tags:
  - Gitea
  - GitOps
  - Automation
---

## Purpose
Choose the documented Gitea configuration-delivery approach that matches the target host and execution environment.  The examples preserve distinct implementations rather than a single interchangeable runner configuration.

## Documented Approaches
- [Docker Runner](<../../workflows/Automation/Gitea/Deliver Configuration with a Docker Runner.md>) — The May 2025 example runs jobs inside the runner container and writes to a bind-mounted destination.
- [Zensical Host Runner](<../../workflows/Automation/Gitea/Publish Zensical Documentation with a Host Runner.md>) — The Zensical-specific example uses a host service account, watchdog permissions, and `/srv/zensical/docs`.
- [Git Repo Updater](<../../deployments/Containers/Docker/Git Repo Updater.md>) — The earlier polling-container approach retains its deployment instructions and canonical watcher script.
- [Why I Adopted Runners](<../../blog/posts/05-16-2025 Learning to Leverage Gitea Runners.md>) — Read the dated account of the watcher limitations and runner experiment.

## Follow the Destination Service
- [Zensical Deployment](<../../deployments/automation/Documentation/Zensical.md>) — Prepare the service and destination before applying the host-runner workflow.
- [Traefik Configuration](<../../deployments/Networking and Access/Reverse Proxies/Traefik.md>) — Identify the dynamic configuration destination before selecting a delivery method.
- [ntfy Notifications](<../../deployments/Applications/Monitoring/Ntfy.md>) — Find the notification service used by the runner examples.

## Related Documentation
- [Related Automation Documentation](<index.md>) — Find the connected deployments, procedures, and references for this subject.