Github is an extra layer of backup, among normal backups.

[edit]

Notable reasons:

- Github runners went oftenly out of space & they were slow. With self hosted runners I don't have these issues anymore because I control the hardware.

Previously I was paying Docker Build Cloud/Depot for performance + Github Pro for extra minutes. Now it's zero cost, superb performance and unlimited minutes.

- I have a centralized registry with private packages and images.

- It's secure, I don't worry if I accidentally make a repo public or leak secrets. I control the access to it in network level.

- I own everything, in case something goes nuts (eg lose access to GH) I'm safe.

Not GP. Probably less dependencies on github, e.g. actions which sometimes don't work. This way github is a "dumb backup".

I selfhost forgejo (gitea fork) on home sever (nuc), similar setup with tailscale. I was planning to setup git mirror on a remote VM for backup, but since I am the only one using it and have everything on dev laptop and remote backups of nuc server I didn't bother to do that (I know I still should).

Because the existence and continued normal operation of the primary is not dependent upon the capricious whims or instability of GitHub.

The self hosting will still be there and working as expected no matter what GH does (fails... again, DMCAs the repo, bans the account, etc.). Self hosting isn't only about being the only one with the data, it's also for the independence aspect. GH as a backup doesn't hinder the independence. Network effects are strong and make a lot of developers still have a GH presence as a secondary platform.

The evolution is when one can finally fully disconnect from GH, the main self hosted platform will continue to operate as if nothing happened.

A migration can have a period of parallel running.

[dead]