Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

How to Host Your Own Private Git Repositories

eklitzke.org

Post reply on HN
Print view View original

111–114 of 114 posts

Re: How to Host Your Own Private Git Repositories

#111

Post by hamburglar »

ethomson wrote: post #102
HelloNurse wrote: post #100

Earlier quoted context omitted.

GitHub etc. need "a ton of maintenance" because of the "fancy tools", which are an unusually complex and sophisticated constantly evolving web application with many users. A private source repository is far less demanding: it's almost never upgraded, and for system administrators it's just another server to keep running and another file system to back up.

I'm not talking about the fancy tools. I'm talking about just serving Git repositories, not about web applications. GitHub is distributing your Git repository across multiple servers in multiple racks in real time for reliability and availability and is the world's largest Git repository hosting provider. Some nice conference talks discuss this, like from Git Merge: https://www.youtube.com/watch?v=f7ecUqHxD7o and Git…

I'm not talking about putting production bits on my own git server, either. I'm talking about how easy it is to create a couple of personal remotes just as a second and third copy of whatever I happen to be working on on my laptop. One goes to my NAS and one goes to my rackspace VM that I keep around for random projects.

I have github and bitbucket accounts, but for little projects, I much prefer the simplicity of effectively just having dupes of my repos on other machines of mine. And it's really nice that the way I interact with them is precisely the way I'd interact with github or repositories at work, despite the fact that they're just directories sitting behind an ssh connection.

Re: How to Host Your Own Private Git Repositories

#112

Post by hamburglar »

stiGGG wrote: post #92
hamburglar wrote: post #87

Earlier quoted context omitted.

Except running a git server is little more than having a place to store a git repo and giving ssh access to it. There's really no maintenance if you already have the server. What github et al provide isn't repo hosting so much as fancy UI tools on top of that. Edit: seriously, I wonder how many people who just automatically go to github have ever bothered to try the simple act of creating a git remote on a file serve…

But the fancy UI tools are the thing the people want. In real world after setting up your ssh on your fileserver, you are ending up in installing gitlab, etc which includes maintaining a database, webserver, ssl certs, etc

Well, I've been pushing my personal code to bare git repos on a rackspace VM for years and I never felt the urge to install gitlab or any of that other fancy stuff, so ... I guess I'm strange? To me, it's very nice to just keep it simple.
Post reply on HN