git server side hooks

How to install and build Git Server using Gitosis in CentOS 6.3 Git, as a distributed version control system, generally communicates with servers over the ssh protocol when using git. The main advantage of using ssh is that it is fast (data is compressed before transmission, faster than HTTP), secure, and easy to read

How to build your own Git ServerGuideNow we will learn how to build a git server, how to write custom Git hooks to trigger corresponding actions (such as notifications) in a specific event, or publish your code to a site. Till now, we mainly discuss how to interact with

/gitosis $ sudo chmod 700/home/gitrepository/ Gitosis stores the repository in the user's repositories directory by default. For example, the git user's repository address is in the/home/git/repositories/directory by default, here we need to create a link ing. Let him point to the repository directory/home/gitrepository that we created previously for storing the project. Ubuntu:/tmp/gitosis $ sudo ln-s/home

configurations of git are started below. 2. Create a git Administrator Account and configure git Create an account (git) as the administrator of the git server and manage project permissions of other users. Ubuntu:/tmp/gitosis $

remote repository and runs it on your computer: $ git clone git@server:/srv/sample.gitCloning into 'sample'...warning: You appear to have cloned an empty repository. The rest of the push is simple. Manage public keys If the team is small, collect everyone's public keys and place them on the serverThe/home/git/. ssh/au

read and write access to each branch or even under each directory. Because Git was developed for Linux source code hosting, Git also inherits the spirit of the open source community and does not support permission control. However, because git supports hooks, it is possible to write a series of scripts on the

pub_path/id_rsa.pub $ {server_ip}: id_rsa.pub. Here we use the direct USB flash drive COPY method. (2) initialize gitosis Go to the directory of the copied id_rsa.pub: CD/tmp Sudo chmod 777 id_rsa.pub Sudo-H-u git gitosis-init At this point, some directories will be generated under the/home/git directory, If you want others to be able To clone the gitosis-admin.git, you need to do the following: Sudo chmo

: 00a @ Ubuntu:/tmp/gitosis $ Sudo chmod A + R/tmp/id_rsa.pub to run gitosis: A @ Ubuntu:/tmp/gitosis $ Sudo-H-u git gitosis-init Initialized empty git repository in/home/prj_git/gitosis-admin.git/ Reinitialized existing git repository in/home/prj_git/gitosis-admin.git/gitosis the interesting thing is that it manages the configuration file through a

a git repository, you need to use the client side to clone it and modify the commit to take effect. git clone ssh://git@127.0.0.1:26732/gitosis-admin.gitRun the git command to clone gitosis-admin. here you need to pay attention to the port problem (this port is the s

Authorized_keysWe then give the post-update a writable permission so that the client can commit the changes.Yourname:gitosis git$ sudo chmod 755/users/git/repositories//gitosis-admin.git/hooks/post-updatePassword:Yourname:.ssh git$ CD ~yourname:~ git$ CD repositories/Yourna

1. Install Jdk-8u172-windows-x64.exe, install with default settingsTwo JRE:C:\Program FILES\JAVA\JDK1.8.0_172\JRE: Dedicated JRE for running the tools contained in the JDK without registry settings.C:\Program files\java\jre1.8.0_172: Public JRE, which can be used by other Java applications, is registered to the registry (Hkey_local_machine\software\javasoft) and the browser.2. Configure Java Environment variablesJava_home:c:\program files\java\jdk1.8.0_172CLASSPATH:.; %java_home%\lib;%java_home%

the test machine and upload the key to the git repository, [Root @ node1 ~] # Useradd-d/opt/user1 user1[Root @ node1 ~] # Echo "user1" | passwd -- stdin user1Change the password of user1.Passwd: All authentication tokens have been successfully updated.[Root @ node1 ~] # Useradd-d/opt/user2 user2[Root @ node1 ~] # Echo "user2" | passwd -- stdin user2Change the password of user2.Passwd: All authentication tokens have been successfully updated.[Root @ n