A month ago, I got drunk on power and decided I’ll be using my own private git server, and I have to admit, it’s been fun, really fun

I got to set up an Authorization system with a git user, create my very own CI/CD pipeline with hooks and docker compose, and watch my site get updated realtime with a reverse proxy that was cannonically hosted on my private git server

But with the highs came the lows, I couldn’t make a PR with git cli, I couldn’t raise an issue or support discussions, and all that was fine when I was writing code for myself, but I’m working on something more than that now

So I got to a cross road where I could either, double down with gitea, or move over to GitHub for my community facing projects

Gitea has a lot of promising features I’ll definitely be keeping at the back of my mind, it’s like a private git repo with UI(and really lightweight). But with its requirement of an account for contribution, it feels like I’m switching to GitHub without its community

So going forward, any of my project that needs a community, will be moving over to GitHub as its source of origin. Maybe in the future I’ll mess around with GitHub’s extensive webhook to take advantage of its community while still hosting my private git server, but for now, I’ll be transitioning my first project over to GitHub

Author’s Notes

It’s a really weird feeling making a logical decision you have an emotional attachment to, but I’m currently only one person with one VM and a lot of ambition. So I’ll be using GitHub’s generous free offers to build my projects and maybe in the future, create a convoluted logic to sync the discussions, issues and PRs with my private repo

I don’t see my portfolio and blog websites being moved over to GitHub, and I definitely still have a lot more I want to do in terms of my CI/CD pipeline, but I thought I’d give an update regardless