Post #2525105

I've self-hosted my own #Forgejo server for a while now and it's been such a freaking delight to work with, and gives me some relief that my code/#Git repos have a place outside of #GitHub. When I started this however, I couldn't fully migrate everything I had to Forgejo - as some were still tied to GitHub's actions and their hosted runners. Before I could migrate them, I'd need to set up runners of my own on the Forgejo server. Seeing GitHub's rapid deterioration lately, I resumed my search on setting up runners on Forgejo the right way, and was initially under the impression that it's gonna be complicated... but as it turns out, it really isn't. I set up a simple runner on a remote #RaspberryPi I had using #Docker (Compose) and it was ready to go. Porting my actions/workflows files were super easy too, unlike doing the same for something like #GitLab. Now all of my repos that were on GitHub and had some CI/CD set up have been migrated to my Forgejo server, using my own runners. I've updated my #Homelab Wiki topic on Forgejo to include the optional step to set up a Forgejo runner. If you're now only considering deploying Forgejo, feel free to check out the rest of the topic which covers the complete setup, some basic recommended configurations, and even how to migrate your repos to Forgejo and set up push mirroring so they still exist on GitHub (if you choose to). 🔗 https://github.com/irfanhakim-as/homelab-wiki/blob/master/topics/forgejo.md#forgejo-runner