IntroductionThis manual will present you the right way to arrange a centralized Git repository, which gives an option identical to a typical subversion work-flow, having a centralized server.
This is not really a problematic technique; its only an extended sequence of relatively easy actions.
Software RequirementsSoftware conditions are the following:
msysgit one.7.0.2 (Customer and Server) CopSSH 3.0.three (Server only) TortoiseGit one.four.4.0 (Customer only) The 32bit versions on the software package deals are linked. If putting in for x64 to the server, substitute installation packages (and paths) appropriately. The x64 versions have not been examined about the server, and only the variations talked about right here have been tested; ymmv.
On The Server Install msysgit 1.7.0.two Find plink, not OpenSSH Pick out Git only on windows path (center choice) Install CopSSH 3.0.3 about the server machine Use default opportunities in the course of set up By default, CopSSH installs to C:System FilesICWModify CopSSH configuration: In C:Program FilesICWetcsshd_config, make sure the following is uncommented and set to "no": PasswordAuthentication no On server, in Windows: Control Panel > User Accounts > Create new account Create an account for each user to whom you wish to allow SSH access. It really is fine for these accounts to be "Limited", or non-Administrators. Activate these new user accounts in CopSSH: Start > Programs > Copssh > "Activate a user" Decide on user account, leave other solutions as default (/bin/bash, etc.) Type a passphrase. You must remember this passphrase: it is associated with the private key of the user being activated. Finish. In C:Program FilesICWhome, there is a subfolder for each user account: Inside each subfolder, send the <user>.key and <user>.key.pub files to the user, along with the pass phrase selected in (5) FOR THAT USER. They will need this information. Make a git repository: Lets assume we want to serve two repos: one on C: drive and one on D: drive On C: C:SeeDriveReposRepo1.git On D: D:DeeDriveReposRepo2.git For each parent folder, e.g. C:SeeDriveRepos: Right Click > Sharing and Security > Security > Users: "Modify" = Checked (note that "Write" becomes checked as well, which is fine) This really is needed for when a remote consumer wants to Push. NOTE: It will be more likely that the central server will host a bare git repository. In this instance, the folder name will be something like SeeDriveReposRepo.git. This does not change the subsequent discussion, except that the URL when specified from the client side must obviously match the folder name above, in terms of Repo.git. Potential Gotcha: If you access and commit into this repository locally, in other words,
Office 2007 Standard, while logged into the server directly, and using file-based access from a clone of this repository about the same server, then the HEADS file representing that branch will take on the security privileges of that user. In other words, doing this while logged in as Administrator will prevent all other non-admin users from modifying that HEADS file: they will be unable to make commits to that branch. There are various workarounds for this, including changing the write permissions to the folder tree of that repository to be valid for all ssh-enabled users, or making all ssh-user accounts (the Windows accounts) administrators, and so on. On server,
Office 2010, ensure that the Firewall has port 22 open. This will allow incoming SSH traffic. Any other port-blocking software or hardware should have the same port open. The ssh server won't be able to find the required Git EXEs yet. Start > CopSSH > Start a unix bash shell. On at least Windows 7, this action must be performed while logged in under an Administrator account. cd /Bin Create a symbolic link to git.exe, git-receive-pack.exe, git-upload-archive.exe, git-upload-pack.exe: $ ln -s /cygdrive/c/ProgramFiles(x86)/Git/bin/git.exe git.exe
$ ln -s /cygdrive/c/ProgramFiles(x86)/Git/libexec/git-core/git-receive-pack.exe git-receive-pack.exe
$ ln -s /cygdrive/c/ProgramFiles(x86)/Git/libexec/git-core/git-upload-archive.exe git-upload-archive.exe
$ ln -s /cygdrive/c/ProgramFiles(x86)/Git/libexec/git-core/git-upload-pack.exe git-upload-pack.exe Around the ClientRequirements for client configurationYou must happen to be given: A private key file, e.g. <user>.key a pass phrase for the same private key a user name to use, e.g. <user> The name of a server, e.g. <server>
Configuration procedure(NOTE: The route for program files below is for Windows XP x64, i.e. C:Plan Files (x86); For 32bit windows,
Office Professional Plus 2007, just use C:Program Files.) Install msysgit 1.7.0.2 Decide upon plink Go for git only on windows path Set up TortoiseGit one.four.4.0 After set up, under Settings > Network > SSH: SSH Client = C:Program Files (x86)TortoiseGitbinTortoisePlink.exe Potential gotcha: if you only deliver the results with other windows developers, you should consider disabling the auto-line-endings adjustment,
Office Professional Plus 2010, and select the choice to leave line endings unchanged. Spurious diffs related to line-endings transformations have been observed. Run C:Program Files (x86)TortoiseGitbinputtygen.exe: The keys generated in CopSSH are OpenSSH keys, but we want to use putty keys with TortoiseGit; right here,
Office Pro Plus 2010, we convert the private key to a putty type. Click button "Load" > Select file <user>.key Save the converted private key somewhere, e.g. <user>.ppk Close puttygen Run C:Plan Files (x86)TortoiseGitbinPageant.exe Add the newly created <user>.ppk Enter the pass phrase for the private key when asked NOTE: On every reboot, Pageant.exe must be started, and the key loaded, and the pass phrase entered. Clone the repositories from the server. Let's start with the C drive repo: find a suitable location, and Right Click > Git Clone: URL = <user>@<server>:c:/SeeDriveRepos/Repo1 If Pageant.exe isn't really running, and/or not correctly set up with the right key and passphrase, then set "Load Putty Key" (yes) = (route to <user>.ppk). Without Pageant.exe, you will be asked for your passphrase on every action. click OK A dialog will come up, asking whether ssh host information should be saved (yes/no): pick yes. The repository should be successfully cloned. If this isn't the case, be certain that that Pageant.exe is running, and has the correct .ppk key loaded. Cloning the repository to the D: drive on the server: URL = <user>@<server>:d:/DeeDriveRepos/Repo2 For repositories about the C: drive for the server, the following URL will also get the job done: URL = ssh://<user>@<server>/SeeDriveRepos/Repo1 This format cannot be used for repositories on other drives on the server.
Office Professional Plus 2007 HOWTO.html
Threaded Mode