Git in the company - hosting your own server

Question

I introduce Git to a 10-person development team who are currently using Visual Source Safe.

They need to host their Git server inside the company. Windows or Linux. Directory authentication is Novell eDirectory.

They need some protection from who can click on the central server.

From:

https://stackoverflow.com/questions/923130/what-type-of-git-server-do-you-use-or-how-do-you-use-git

Perhaps the workflow might be:

• Install 10 users on the server.
• Set up a shared directory for the server file system in which 10 users have write access to
• Push files to the server via SSH, for example Git push [e-mail] : user1 / project.git
• But then I need the keys to be installed on the server

Question Does anyone use a workflow like this is successful in a company. What works? It starts to feel like most people use Git with GitHub, etc.

[Change]: see Selecting the source control system: logical next steps after VSS Git may not be suitable for this command.

Answer 1

Of course, it is possible to have a standalone git repository with access control. As a rule, you need to create an account with the name git on the server machine, install the shell of this account in git-shell , which is a limited shell intended for use only with git, and then put the public keys for each authorized user in the git file -user.ssh / authorized_keys.

http://blog.commonthread.com/2008/4/14/setting-up-a-git-server contains most of the rest of the details.

Answer 2

We use gitosis where developers push and pull. See gitosis .

Answer 3

This is pretty much the technique I use. It is a hassle to set up accounts and keys for everyone, but you only need to do this once.

As a bonus, if you get it right, you can have a read-only repository available in git: // independently or http: // whatever and your writable repository in git + ssh: // independently.

EDIT: gitosis looks pretty neat, although you might want to have separate accounts for all of your developers at some point.

Answer 4

At the same time, the world has changed a lot, and I think that http://gitblit.com/ is currently one of the best solutions (depending on your requirement):

• You can easily configure HTTPS.
• Integrates with LDAP.
• Allows you to define groups / teams and exercise precise control of access to repositories.
• It is open source, so cheap to install (compared to Github and others). A.

So, if you do not want to have a new server for each team, this is really an option. We like it!

Answer 5

There are many git GUIs if you want to run it yourself. gitorious is nice, for example.

For your authentication needs, which is largely up to you. You may have a hard time when ssh is following your preferred auth technique (last time I did something like this, I changed ssh to read keys from LDAP).

The web interface could do anything, I'm sure. I would probably just leave it open inside the network.

Answer 6

Im totally surprised that no one mentioned running open source projects: http://gogs.io , which basically offers the same thing that gitlab does (without including Wiki, code overview, code snippets), but with minimal system resources (low footprint), which is ideal for working in a raspberry Pi, for example. Installation and maintenance are also easier.

Answer 7

I will be a little interested in suggesting git for your version control system. Security Visual Source is like a Microsoft product that you can get, and git is on a different level and almost doesn't work on Windows.

TortoiseGit , the Windows git interface is now available. This annoys me my initial answer, as I feel that accessing the GUI for your version control system is very important for most Windows developers.