I'm self-hosting Gitea and Woodpecker CI for least 6 years, alongside my own docker and pypi registries. Adding x86 and ARM runners, it costs me circa $30/month to run the whole thing, and I am reasonably sure that I could make the whole thing scale at a lower cost per user than what Github charges.

I am seriously, 100%, contemplating the idea of offering consulting for migrating companies and projects out of Github. Given that I am fully employed, I'd only be able to do this on the weekends. Could I get a show of hands to get an idea of potential customers?

▲

ramon156 2 hours ago | parent | next [-]

Doing the same thing, and I'd join you in this consulting haha. It's a breath of fresh air to know what your CI is actually doing

▲

herpdyderp 2 hours ago | parent | prev | next [-]

Sounds interesting but I'm just going to do the same thing as you (self host).

▲

BowBun 2 hours ago | parent | prev [-]

I work at a startup with ~20-30 devs. We're talking about a project like this. I'm not sure weekends would work for an actual company, though maybe it depends. I think there would be an appetite for this. From my POV - the main areas of interest are how you can roll this out to a team gracefully without breaking everyone's workflows for multiple days. Good luck

	▲	rglullis an hour ago \| parent [-]
		The most natural way to roll this out would be to have a "blue/green" system, where both systems are running and the weekends would be the time to take the steps towards the migration. First set up the servers, integrate Auth/SSO (depending on the current company set up), etc. That could be done probably in a single weekend. Once this is done, the team would have two possible git remotes to work with. Given that gitea also allows mirroring with Github, the team would be able to even switch to Gitea as the "main" git remote and for PR reviews even if the CI part is still on Github. The harder part would be migrating the CI jobs. But this also can be done in parallel and no one needs to cut out their Github actions immediately. Start with the simplest of the stages, e.g, the automated test suite, and once you get the whole pipeline from Woodpecker on an staging environment, you'd could take another weekend to test the whole workflow. Once the first project is successfully migrated, it becomes a matter of repeating the process. Woodpecker is still a bit finicky and debugging it can be a bit annoying, but given that it's all based on docker it is a lot easier to debug a pipeline locally.