Recent searches
Search options
Administered by:
@nicr9@techhub.socialPart of my project for adopting gitops in my homelab has been setting up git hosting. I've selected Gitea for this instead of Gogs because I thought I'd have an easier time bootstrapping fluxcd...
Now that I've had more time to sit with the docs and learn more about Gitea, I've noticed they have broad support to serve as package registries too! It seems like I can host helm charts and docker images alongside my infra as code! This is fantastic, it'll greatly simplify my architecture. Two birds, one container!
@nicr9
Before you are too invested, did you check out their fork forgejo? It's the software running codeberg.org
@jakob42 I did! I like the focus on keeping things open and I saw that they acted on a CVE before gitea did which all looks good to me 
I had to make a choice to get started and some of the integrations I was looking at (fluxcd, tofu, atlantis, etc) all mentioned support for gitea so I guess I jumped the gun a little. I've looked at things more closely since then and I'm thinking these integrations will likely interoperate with Forgejo just fine.
My current plan is to stick with Gitea for a while (my priority really is fluxcd) and eventually try a migration. I'm not particularly worried about the effort involved and I'll keep all my repos backed up so even if it all goes sideways I can rebuild from scratch.
What are your thoughts on the fork? Are you using it yourself (or just codeburg?)
@nicr9
I'm using it happily and it feels like the successor to gitea, especially if FOSS is your focus. (Gitea, while AFAIK is FOSS, is owned by a for profit company)