How to build git on linux
Method: 1. Use the "yum install git" command to install git; 2. Use the "adduser git" command to create a git user; 3. Use the "ssh-keygen-t rsa" command to create a public key; 4. Use the "git init --bare" command to initialize the git repository.
The operating environment of this tutorial: linux7.3 system, Git version 2.30.0, Dell G3 computer.
How to build git on linux
1. Install git
First install git, generally For now, the server already has a built-in git installation package, and we only need to execute a simple installation command to install it. For example:
$ yum install git # centos $ apt-get install git # ubuntu
The above is to log in to the server directly with root to operate, and it is also for the convenience of demonstration.
Git is different from mysql. When installing mysql, you must install mysql-server, which is the mysql server. Git is distributed. Every computer with git installed is both a client and a server. Git and Git can communicate with each other, and our so-called git server is actually not fundamentally different from our own computer. However, in order to manage the project more effectively, we all adopt a centralized management method, so we create a "git server" as the final terminal for everyone else to submit code.
2. Create git user and permissions
Of course we are not allowed to use root directly for communication and interaction, so we create a git user for future code submission User.
$ adduser git
After executing this command, you find that there is an additional git directory in the /home directory. Logically speaking, now there is this git user in your system, and the home directory is in /home/git . However, we do not want this user to connect to the server through ssh, so we must prohibit this user from using ssh to connect to the server for operations. We handle it by editing a permissions file:
$ vi /etc/passwd
Find /bin/bash similar to
git:x:1001:1001:,,,:/home/git:/bin/bash
at the end, which is the permission that allows ssh connection operations, we change it to /user/ bin/git-shell, the result is as follows:
git:x:1001:1001:,,,:/home/git:/usr/bin/git-shell
If handled in this way, git will not be able to connect via ssh (actually it is possible, but it will crash).
We also have to assign a password to git, execute:
$ passwd git 123456(你的密码)
This password will be used when you submit the code later.
3. Public key
This is a special step in git. When communicating, the client and server need a certificate for verification. First generate a public key:
$ cd ~ $ ssh-keygen -t rsa
Now you have a public key on your computer, but where is it? In the .ssh directory, folders starting with . are hidden, but you can cd into them.
$ cd .ssh $ vi id_rsa.pub
Now you can see your public key, copy all the contents. Next, we go back to the server to operate.
$ cd /home/git/ $ mkdir .ssh $ cd .ssh $ vi authorized_keys
If it is a bare metal machine, there should be no .ssh directory in the /home/git directory on the server, so we create it ourselves. After opening (automatically created) authorized_keys, paste the public key we just copied into it, ok OK, save and exit.
4. Initialize a git repository
I am used to throwing this kind of things into /var, so we create a git directory under /var
$ cd /var $ mkdir git $ chown -R git:git git $ chmod 777 git $ cd git
Next, we use the git command to initialize a warehouse:
$ git init --bare arepoforyourproject.git
After the initialization is completed, the empty warehouse will be OK.
Note: The .git directory must have read and write permissions, because when we push, we use the git user to push to the server, and there will be a writing process. If it is not granted writable permission, push will fail.
5. Try cloning
Try cloning to see if the warehouse can be used:
$ git clone git@10.0.0.121:/var/git/arepoforyourproject.git
Then you will be prompted to enter your git password, enter Go in, and you will be prompted again to clone a blank repository. This means that the server is OK.
Related recommendations: "Linux Video Tutorial"
The above is the detailed content of How to build git on linux. For more information, please follow other related articles on the PHP Chinese website!

Hot AI Tools

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Undress AI Tool
Undress images for free

Clothoff.io
AI clothes remover

Video Face Swap
Swap faces in any video effortlessly with our completely free AI face swap tool!

Hot Article

Hot Tools

Notepad++7.3.1
Easy-to-use and free code editor

SublimeText3 Chinese version
Chinese version, very easy to use

Zend Studio 13.0.1
Powerful PHP integrated development environment

Dreamweaver CS6
Visual web development tools

SublimeText3 Mac version
God-level code editing software (SublimeText3)

Hot Topics



How to use Docker Desktop? Docker Desktop is a tool for running Docker containers on local machines. The steps to use include: 1. Install Docker Desktop; 2. Start Docker Desktop; 3. Create Docker image (using Dockerfile); 4. Build Docker image (using docker build); 5. Run Docker container (using docker run).

Docker process viewing method: 1. Docker CLI command: docker ps; 2. Systemd CLI command: systemctl status docker; 3. Docker Compose CLI command: docker-compose ps; 4. Process Explorer (Windows); 5. /proc directory (Linux).

Troubleshooting steps for failed Docker image build: Check Dockerfile syntax and dependency version. Check if the build context contains the required source code and dependencies. View the build log for error details. Use the --target option to build a hierarchical phase to identify failure points. Make sure to use the latest version of Docker engine. Build the image with --t [image-name]:debug mode to debug the problem. Check disk space and make sure it is sufficient. Disable SELinux to prevent interference with the build process. Ask community platforms for help, provide Dockerfiles and build log descriptions for more specific suggestions.

VS Code system requirements: Operating system: Windows 10 and above, macOS 10.12 and above, Linux distribution processor: minimum 1.6 GHz, recommended 2.0 GHz and above memory: minimum 512 MB, recommended 4 GB and above storage space: minimum 250 MB, recommended 1 GB and above other requirements: stable network connection, Xorg/Wayland (Linux)

The reasons for the installation of VS Code extensions may be: network instability, insufficient permissions, system compatibility issues, VS Code version is too old, antivirus software or firewall interference. By checking network connections, permissions, log files, updating VS Code, disabling security software, and restarting VS Code or computers, you can gradually troubleshoot and resolve issues.

VS Code is available on Mac. It has powerful extensions, Git integration, terminal and debugger, and also offers a wealth of setup options. However, for particularly large projects or highly professional development, VS Code may have performance or functional limitations.

VS Code is the full name Visual Studio Code, which is a free and open source cross-platform code editor and development environment developed by Microsoft. It supports a wide range of programming languages and provides syntax highlighting, code automatic completion, code snippets and smart prompts to improve development efficiency. Through a rich extension ecosystem, users can add extensions to specific needs and languages, such as debuggers, code formatting tools, and Git integrations. VS Code also includes an intuitive debugger that helps quickly find and resolve bugs in your code.

How to back up VS Code configurations and extensions? Manually backup the settings file: Copy the key JSON files (settings.json, keybindings.json, extensions.json) to a safe location. Take advantage of VS Code synchronization: enable synchronization with your GitHub account to automatically back up all relevant settings and extensions. Use third-party tools: Back up configurations with reliable tools and provide richer features such as version control and incremental backups.
