【基础篇】Eclipse + gitLab + ssh连接

来源:互联网 发布:淘宝虚拟物品怎么发货 编辑:程序博客网 时间:2024/05/18 22:40

先来点gitLab官网上的说明:怎么生成SSH keys

SSH keys

An SSH key allows you to establish a secure connection between your computer and GitLab. Before generating an SSH key in your shell, check if your system already has one by running the following command:

Windows Command Line:

type %userprofile%\.ssh\id_rsa.pub

GNU/Linux/Mac/PowerShell:

cat ~/.ssh/id_rsa.pub

If you see a long string starting with ssh-rsa, you can skip the ssh-keygen step.

Note: It is a best practice to use a password for an SSH key, but it is not required and you can skip creating a password by pressing enter. Note that the password you choose here can't be altered or retrieved.

To generate a new SSH key, use the following command:

ssh-keygen -t rsa -C "caopengli@financeyouth.cn"

This command will prompt you for a location and filename to store the key pair and for a password. When prompted for the location and filename, just press enter to use the default. If you use a different name, the key will not be used automatically.

Use the command below to show your public key:

Windows Command Line:

type %userprofile%\.ssh\id_rsa.pub

GNU/Linux/Mac/PowerShell:

cat ~/.ssh/id_rsa.pub

Copy-paste the key to the 'My SSH Keys' section under the 'SSH' tab in your user profile. Please copy the complete key starting with ssh-rsa and ending with your username and host.

To copy your public key to the clipboard, use the code below. Depending on your OS you'll need to use a different command:

Windows Command Line:

type %userprofile%\.ssh\id_rsa.pub | clip

Windows PowerShell:

cat ~/.ssh/id_rsa.pub | clip

Mac:

pbcopy < ~/.ssh/id_rsa.pub

GNU/Linux (requires xclip):

xclip -sel clip < ~/.ssh/id_rsa.pub

Deploy keys

Deploy keys allow read-only access to multiple projects with a single SSH key.

This is really useful for cloning repositories to your Continuous Integration (CI) server. By using deploy keys, you don't have to setup a dummy user account.

If you are a project master or owner, you can add a deploy key in the project settings under the section 'Deploy Keys'. Press the 'New Deploy Key' button and upload a public SSH key. After this, the machine that uses the corresponding private key has read-only access to the project.

You can't add the same deploy key twice with the 'New Deploy Key' option. If you want to add the same key to another project, please enable it in the list that says 'Deploy keys from projects available to you'. All the deploy keys of all the projects you have access to are available. This project access can happen through being a direct member of the project, or through a group. Seedef accessible_deploy_keys in app/models/user.rb for more information.

Deploy keys can be shared between projects, you just need to add them to each project.

Applications

Eclipse

How to add your ssh key to Eclipse: https://wiki.eclipse.org/EGit/User_Guide#Eclipse_SSH_Configuration

Tip: Non-default OpenSSH key file names or locations

If, for whatever reason, you decide to specify a non-default location and filename for your GitLab SSH key pair, you must configure your SSH client to find your GitLab SSH private key for connections to your GitLab server (perhaps gitlab.com). For OpenSSH clients, this is handled in the ~/.ssh/config file with a stanza similar to the following:

## Main gitlab.com server#Host gitlab.comRSAAuthentication yesIdentityFile ~/my-ssh-key-directory/my-gitlab-private-key-filenameUser mygitlabusername

Another example

## Our company's internal GitLab server#Host my-gitlab.company.comRSAAuthentication yesIdentityFile ~/my-ssh-key-directory/company-com-private-key-filename

Note in the gitlab.com example above a username was specified to override the default chosen by OpenSSH (your local username). This is only required if your local and remote usernames differ.

Due to the wide variety of SSH clients and their very large number of configuration options, further explanation of these topics is beyond the scope of this document.

Public SSH keys need to be unique, as they will bind to your account. Your SSH key is the only identifier you'll have when pushing code via SSH. That's why it needs to uniquely map to a single user.



主要有这么几步:生成key,添加key到服务,创建连接

1.生成key

我们用的是eclipse自带的生成key的工具,windows->preferences,找到SSH2.

Gitlab+eclipse+ssh连接

在key management处点生成RSAkey

Gitlab+eclipse+ssh连接

后面输入key的说明和密码,密码也可以空着。点save private key. 把生成的key文件存到用户目录的.ssh目录下。(像第一张图中SSH2 Home指定的目录)

Gitlab+eclipse+ssh连接

会生成两个文件,一个id_rsa是私钥,一个id_rsa.pub是公钥。

2.发布公钥到服务器

用记事本打开id_rsa.pub文件,能看到如图的示的类似内容,把它们复制下来。

Gitlab+eclipse+ssh连接

用你的用户登陆到gitlab,profiles->ssh keys->add ssh kay。给用户添加全局的公钥文件。

Gitlab+eclipse+ssh连接

把刚才复制的内容贴到页面上,add key.

Gitlab+eclipse+ssh连接

3.连接到服务器

这里我们是在一个新的环境下建立到gitlab的连接,打开git repositories,点clone一个git库

Gitlab+eclipse+ssh连接

这里的URL输入在gitlab的项目中显示的连接。这里要解释下这个连接的内容。

第一个git,git@server :git/gittest.git,是在gitlab所在的那个linux系统中,用来管理git库的一个linux系统用户,默认这个用户的密码是空的。所以下图中下面的密码处为空。

@后面是服务器地址git@server:git/gittest.git

:后面,git@server :git/gittest.git ,是创建这个项目的那个gitlab用户的用户名,这里我们的用户名也是git

/后面,git@server :git/gittest.git,就是你的项目名。

.git是后缀

Gitlab+eclipse+ssh连接

如果第一次与服务器建立连接。会寻问是否保存服务器上的公钥信息,点yes。

Gitlab+eclipse+ssh连接

在这之后会提示你输入你在建立key文件时输入的密码。next.就能看到已经选择的一个分枝了。

Gitlab+eclipse+ssh连接

next,同步文件,在git repositories就能看到这个同步下来的库了。

Gitlab+eclipse+ssh连接

在项目名上点右键,import projects,把同步下来的项目导入到eclipse

Gitlab+eclipse+ssh连接

完成。

问题:有时会出现生成的key文件不能正常使用,在连接服务时会问几次密码后中断,可以尝试重启eclipse

0 0
原创粉丝点击