Gitea
Gitea
Gitea is the self-hosted Git service and CI/CD platform that OMEGA Core's own engineering work runs on — source control, pull requests, and the Actions pipeline that builds and deploys this site.
It replaced GitHub as the primary host on 3 July 2026, in keeping with OMEGA's preference for self-hosted, on-premise infrastructure over external SaaS wherever practical.
Infrastructure
Host
Proxmox LXC — CT 108
Unprivileged container, static internal address
Access
gitea.internal.omegaproject.ai
Reverse-proxied through npmplus — see the DNS and reverse-proxy integrations
CI/CD
Gitea Actions
Self-hosted runner (CT 109), builds and deploys this site on every push to main
Backup
GitHub — passive mirror
One-way push mirror only. Not used for day-to-day work, no Actions run there
Login
Local + Authentik (optional)
Authentik SSO is account-linked to the existing admin login — an additional path, not a replacement for it. See Authentik
Role in OMEGA Core
Gitea hosts the repository behind everything documented on this site, plus the project's other repos. Its Actions pipeline is what actually ships changes — a push to main triggers a self-hosted runner that builds the site and deploys it to S3/CloudFront.
AI-authored engineering work — including the work behind several of the pages on this site — commits under its own dedicated service account rather than the project owner's personal identity, so git history and blame honestly distinguish who did what.
Security
Branch Protection
main requires an approving review before merge; only the repository owner's account is permitted to bypass that rule.
Least Privilege
The automation account used for AI-authored commits holds write-only collaborator access — not admin, not the owner's own credentials.
Runner Isolation
The self-hosted Actions runner lives in its own unprivileged LXC, separate from the Gitea service itself.