Detailed introduction to dual git configuration

This article mainly shares with you the weird dual git configuration, hoping to help everyone.

Due to actual development needs, the company uses Gitlab, and I use Github privately. I want to configure both on the company computer at the same time.
There are many tutorials on the Internet for this configuration. I followed this tutorial at first, but they all failed. In the end, I succeeded based on my own operation. Realized the coexistence of Github and Gitlab.

1. Configure your own Github

• ##1.1. Under your own C:\Users\william folder , create a new .ssh folder through the command line tool mkdir .ssh;

• 1.2, cd .ssh, through ssh-keygen -t rsa - C "My email address" generates a pair of RSA keys for your own github, enter all the way until the end is successful

• 1.3, and then add the .ssh file Open the id_rsa.pub file in the folder, copy the contents and add it to the ssh of the github web version

• 1.4, through ssh -t git@github .com to test connectivity, where you can enter yes in Are you sure you want to continue connecting (yes/no)?

2. Configure yourself Gitlab

• 2.1, basically based on the company's configuration document, the basic operation is the same as above

3. Summary and Thoughts

• 3.1.1. Finally my. There are only config, id_rsa, id_rsa.pub, and known_hosts files in the ssh folder. Among them, I added the Github domain name pointing to the config file, otherwise the ssh -t git@github.com prompt failed.

• 3.1.2. According to the online tutorials, they may not be suitable for your own company. The main variable is that each company may have certain environment variables when configuring Gitlab. The difference is reflected in the different contents of the config file in the final .ssh folder and the known_hosts file, mainly the config file. Therefore, you must explore according to your own company's situation and find a configuration path that suits your situation. I spent most of the day reading several online tutorials but failed.

• 3.1.3. After github generates its own pair of RSA keys for github through ssh-keygen -t rsa -C "my email address", Enter file in which to save the key (C:\Users\william/.ssh/id_rsa): will let you choose a custom file name to save the key. If I do not enter, I will set my own custom file name, even if I put The generated public key was added to the SSH of the web page, and the final connectivity test failed. Of course, it cannot be cloned. It feels very strange.

• 3.2.1. Why do you customize Github? Does the last connectivity test of the key file name fail?

• 3.2.2. Why is it that after Gitlab customizes the file name, the final file name is still the default id_rsa, strange! ! !

• 3.2.3. There are only config, id_rsa, id_rsa.pub, and known_hosts files in the .ssh folder, but it can be connected to Github and Gitlab respectively. Indeed Very strange. You read that right, id_rsa and id_rsa.pub are only Gitlab keys, and Github ones are gone. Weird! ! ! !

Related recommendations:

The above is the detailed content of Detailed introduction to dual git configuration. For more information, please follow other related articles on the PHP Chinese website!