Technical
Gitea Hub
A private code hub workflow for provisioning a client Gitea organization, importing GitHub repositories, and indexing code, issues, releases, and wikis into CaveauAI.
Public and internal interfaces
These are the main routes, handlers, and integration surfaces used by this product area.
GET /api/portal/gitea/status
POST /api/portal/gitea/provision
POST /api/portal/gitea/migrate
POST /api/portal/gitea/repos/{id}/toggle
POST /api/portal/gitea/repos/{id}/sync
POST /api/portal/public/gitea-webhook
Architecture notes
- The page calls the portal Gitea handler and queues background workers for sync jobs.
- Imported repositories are discovered inside the client organization.
- Safe indexing excludes high-risk or low-value files before creating corpus documents.
Access and permissions
App pages are authenticated through the shared bnl_session cookie unless explicitly marked public. Public docs should describe integration behavior without including secrets, private tokens, private IPs, or tenant-specific records.
Troubleshooting
- Upgrade screens mean the plan is below the required tier.
- Configured false means the server lacks Gitea service setup.
- Long imports usually involve large issue or PR histories and GitHub rate limits.