DevOps & CI/CD Workloads
Git hosting and CI/CD runners for development workflows.
Available Workloads
Section titled “Available Workloads”Forgejo
Section titled “Forgejo”Self-hosted Git service (Gitea fork) with Actions support.
Features:
- Git repository hosting
- Pull requests and code review
- Issue tracking
- GitHub Actions compatible CI/CD (Forgejo Actions)
- Lightweight and fast
- Built-in package registry
Use Cases:
- Private Git hosting
- Code collaboration
- CI/CD pipelines
- Package management
Deployment:
loko workloads add forgejo --nowloko workloads connect forgejoEndpoints:
- Web UI:
https://forgejo.${LOKO_DOMAIN} - Git HTTPS: Port 3000 (SSH disabled for simplicity)
Default Credentials:
- Username:
forgejo - Password: Auto-generated (use
loko workloads connect forgejo --show-password)
Git Operations:
# Clone via HTTPS (SSH disabled)git clone https://forgejo.${LOKO_DOMAIN}/username/repo.git
# Push changesgit push origin mainChart: forgejo-helm/forgejo
Forgejo Runner
Section titled “Forgejo Runner”CI/CD runner for Forgejo Actions (GitHub Actions compatible).
Features:
- GitHub Actions workflow syntax
- Docker-based execution
- Automatic registration with Forgejo
- Parallel job execution
Deployment:
# Automatically deploys with Forgejo# Or deploy separately:loko workloads add forgejo-runner --nowWorkflow Example:
# .forgejo/workflows/test.ymlname: Teston: [push]jobs: test: runs-on: ubuntu-latest steps: - uses: actions/checkout@v3 - name: Run tests run: | echo "Running tests..." npm testChart: forgejo-runner/forgejo-runner