[szek]

I think the point is not about backups. It is really, really easy to set up a remote git repository. Everything is nicely documented in chapter 4 of Pro Git [1]. Because a git remote is nothing more than a plain directory, you could serve a git repo anywhere you could store files, even on your own disks.

If multiple people need push access to a private repository, just serve a central repository as on a VPS and use SSH for authentication. I am not sure if there is a reason to use a third party hosting service for this, especially when hosting private repos.

[1]: https://git-scm.com/book/en/v2/Git-on-the-Server-Getting-Git...

[k00b]

> just serve a central repository as on a VPS and use SSH for authentication

Reminds me of this comment https://news.ycombinator.com/item?id=9224

Edit: I don't mean to dismiss your comment. I just mean to say I'm obviously comfortable doing what you described but it's not a trivial amount of effort even if it is conceptually straightforward.

[saagarjha]

It's a little bit of work, but really it's surprising how well Git works with the dumbest servers. I run a number of Git mirrors off a $5 VPS served from a folder that I run python3 -m http.server in; it's literally just that and it works beautifully.

[gigatexal]

And what about ssl?

[saagarjha]

Ignored ;)

[k00b]

Agreed, git is great!