The security conscious may wish to check that the SHA256 hash is the same as that shown above. You will therefore need to type yes to confirm that you would like to connect. Note that the first time you connect to the Chime server, SSH does not know the identity (public key) of the Chime server. Remote: Total 26 (delta 2), reused 0 (delta 0) Remote: Compressing objects: 100% (14/14), done. Warning: Added 'chime.cl.cam.ac.uk,128.232.21.23' (RSA) to the list of known hosts. No matching host key fingerprint found in DNS.Īre you sure you want to continue connecting (yes/no)? yes RSA key fingerprint is SHA256:nEryDfQuwSCP9HxY/aC8wTjyPVBGBZQNMvYHxy+hiWI. The authenticity of host 'chime.cl.cam.ac.uk (128.232.21.23)' can't be established. On your computer check you have correctly configured everything by using the git command line tool to clone the repository in a terminal (making sure you use your own URI for the repository name!):īash$ git clone into 'further_java_ticklet_0'. You can use the URI to clone this repository, in other words, make a local copy, by transferring the data over the SSH protocol to your computer. Under the task description is a URI (of the form where crsid is your CRSID). You can browse the files and directories in the repository using the web interface. You should now see an overview page for your repository. Go to, edit the repository name if you wish to change the default, and then click on the Start task button. From there you will be able to test your work via the web interface.įirst, let's copy the official repository for Ticklet 0, and check that you have setup SSH properly, as described in the previous section. Once you are ready to test your code, you should push your changes from your local repository to the remote repository hosted on Chime. You should regularly stage and commit changes you make to files in your local repository (more details to come) this allows you to look back in time at the history of your changes if you, say, accidentally delete a file by mistake. You can then work on this local copy (without Internet connectivity, if required). In brief, you create your own copy of the starting point into your own Git repository, then make a local copy of your version of the repository (a clone) on your MCS machine or laptop.
You will need to carry out the steps described in this section once for each Ticklet. There is a separate Git repository associated with each Ticklet for this course. You can do this at any point.Ĭlone, edit, stage, commit and push with Git You should repeat the above steps for each additional computer you wish to associate with your Chime account.
To do so, go to, entering your Raven credentials as necessary.Ĭlick on the SSH keys menu icon at the very top of the screen.Ĭopy and paste the public key into the SSH Key field. On MCS machines, we recommend entering a passphrase when prompted to provide additional protection for your private key.Ĭopy your public key into Chime so you can access Chime using the SSH protocol.
Intellij git add remote repository code#
Please protect your private key as it can be used to submit code for this course on behalf of you (as well as other actions if you use SSH more generally). By default, on MCS machines, ssh-keygen will generate a new private key and place it in ~/.ssh/id_rsa and public key in ~/.ssh/id_rsa.pub. Run ssh-keygen in a terminal to generate a new public-private key pair.
0 kommentar(er)
