Comment by cdrnsf

I have moved to self-host Forgejo a few years ago and I can also highly recommend. It's working great. I have posted a tutorial [1] (verified last month that it still works), and recently moved from Hetzner to 2 Raspberry Pi's for hosting the server and the runner [2]. It's great. Really rock solid. Has been more reliable and faster than GitHub.

[1]: https://huijzer.xyz/posts/55/installing-forgejo-with-a-separ...

[2]: https://huijzer.xyz/posts/55/installing-forgejo-with-a-separ...

Yes, this.

I was self hosting gitlab for a long time. But forgejo is an order of magnitude less resource intensive.

It is a single very small go binary. You can use sqlite or postgres. But you can easily run it inside a small docker container on your local machine.

And it is fun to hack on it because it is so open. You build really fun workflows that are blocked by the corporate limits of Github.

I did the same a few months ago when I read that multiple big OSS Linux projects were moving to it and it's been phenomenal so far.

Same. I installed Forgejo two months ago when Github wouldn't let me create agent accounts. It's been awesome. Any time I want a new feature I open my agent on the server and tell it to add the feature to Forgejo. Took all of 15 minutes for it to add a working Show/Hide "Viewed" files on the PR reviews.

Same, I've been enjoying it a ton. Recently, with the help of Claude, I've used it to set up an entire CI/CD pipeline for my home server. The flow is roughly:

Build Nix config into a VM image => Deploy VM to Proxmox via its API => Spin up Docker stack via Komodo

I've also trying to use it to sync my Obsidian vault via git to my phone, altho that flaked out on me recently (if anyone knows a reliable way to use git via the shell on iOS, please let me know).

Same - also installed a forgejo runner via docker so i've got CI. Forgejo has it's own artifactory/registry so the apps I make get a docker image and I just run that docker image. All on my own hardware.

Same! I've also recently exposed mine to the internet through a fly.io proxy, though. So far, no issues, but I'm keeping a close eye.

I went with gitea, but for the same general reasons. I like It has the option to mirror repos up to GitHub for the stuff I actually want to share with the world. Is there anything that made you choose forgejo specifically? I’m not eager to move platforms, but I know there’s more options that have popped up in the years since I first stood up my gitea instance.