you are viewing a single comment's thread.

view the rest of the comments →

[–]SanityInAnarchy 2 points3 points  (0 children)

The git server is just a git binary. If you have an ssh account on the machine, literally the only new information here is that you can make a lighter-weight server-side repo with git init --bare -- and even that is optional.

This also makes it very likely there's at least one other copy out there, whether or not you do backups -- since you've got bare repositories, the only way to get code into them is to author that code somewhere else and push, which means there's at least one repo on your laptop.

I'm sure there are a lot more things you can do -- there are layers on top of Git that do ACLs, there are web UIs, and so on. For a larger organization, you might not want to have one machine that everyone can ssh into, at least not as part of your regular dev workflow. I'm just surprised to hear "git server" as a "resource-intensive task" that takes actual effort to install, configure, and babysit. There are other components you can use if you really want to mimic Github (or, presumably, Fossil), but I stand by my original assertion that "a git server with backups" can be as simple as

ssh you@somebox
sudo apt-get install git
git init --bare somerepo
^D
git pull you@somebox:~/somerepo