# Ticket: Open-source GitHub alternative service

## Metadata
- Type: Ticket
- Status: Inbox
- Project: Homelab Operations
- Created: 2026-06-06
- Updated: 2026-06-06
- Priority: Medium

## Goal

Select and deploy an open-source GitHub alternative for hosting homelab/project repositories, issues, pull requests, code review, and agent collaboration.

## Why

The user wants better separation between projects and potentially separate git repositories. A self-hosted Git service would provide a central place for repos, branches, issues, PRs, and collaboration between agents/humans.

## Scope

Included:
- Research options such as Forgejo, Gitea, GitLab CE, and potentially SourceHut-style tools
- Choose an MVP service
- Plan deployment target: VM/LXC, storage, DNS, TLS, backups, updates, and admin access
- Integrate with the VM/LXC template standard
- Define repo organization model for Nimrod, service repos, and infra-as-code repos

Not included:
- Migrating every existing project immediately
- Public internet exposure unless explicitly approved
- Full CI/CD implementation in the first pass unless selected as MVP requirement

## Acceptance Criteria

This ticket is done when:
- [ ] Options are compared against homelab needs
- [ ] Target service is selected
- [ ] Deployment spec is written
- [ ] VM/LXC resources are allocated through the Proxmox registry
- [ ] DNS/TLS/backup/update expectations are documented
- [ ] Service is deployed and reachable
- [ ] At least one test repository is created

## Questions

- Should the service be LAN-only or externally reachable through VPN/reverse proxy?
- Is lightweight Forgejo/Gitea preferable to heavier GitLab CE?
- Should issue tracking live in this Git service, Nextcloud, or remain markdown-first in Nimrod?
- Should CI runners be part of the initial deployment or deferred?

## Plan / Next Actions

- [ ] Research Forgejo/Gitea/GitLab CE tradeoffs
- [ ] Pick MVP option
- [ ] Draft deployment spec using DevOps QRSPI
- [ ] Deploy only after Proxmox lock/registry process is in use

## Notes

- This ticket should be coordinated with `2026-06-06-repo-and-agent-workspace-isolation.md`.