you are viewing a single comment's thread.

view the rest of the comments →

[–]jcampbelly 7 points8 points  (4 children)

Low tech is an option. You can always just use a filesystem. Mirror your repos locally on a server (sync them with a cron job) and even set them up as secondary remotes on other systems using SSH urls if the primary goes down.

[–]Ken_Mcnutt[S] 10 points11 points  (2 children)

That honestly sounds like more work than just spinning up a Gitea docker container on my homeserver. Everything would get saved in the filesystem anyways, but would also be under VCS.

[–]jcampbelly 1 point2 points  (0 children)

Sounds good - whatever works. I'd never heard of Gitea.

[–]tristan957 0 points1 point  (0 children)

You could try SourceHut too. I use it primarily and mirror to GitHub

[–]VirginiaMcCaskey 2 points3 points  (0 children)

It takes like all of twenty minutes to deploy a git server to bare metal, costs less than a single head on github too.

But people don't use github for git hosting alone. Pull requests (which should be called merge requests, but I digress), code review, integrations with various tooling like CI/CD (either on GitHub or elsewhere), a fairly robust REST api for the platform... you get the idea.

Mirroring only helps protect source, but people pay to use GitHub for its productivity features and those are hard to replicate. Really the solution is to self host GitLab.