From 4958b3e6d038acfbad8b974ed927f10f62f8b17c Mon Sep 17 00:00:00 2001 From: Cameron McEfee Date: Tue, 22 Feb 2011 18:39:40 -0800 Subject: Added bootcamp files --- _posts/2011-02-15-win-set-up-git.markdown | 157 ++++++++++++++++++++++++++++++ 1 file changed, 157 insertions(+) create mode 100644 _posts/2011-02-15-win-set-up-git.markdown (limited to '_posts/2011-02-15-win-set-up-git.markdown') diff --git a/_posts/2011-02-15-win-set-up-git.markdown b/_posts/2011-02-15-win-set-up-git.markdown new file mode 100644 index 0000000..bdbf163 --- /dev/null +++ b/_posts/2011-02-15-win-set-up-git.markdown @@ -0,0 +1,157 @@ +--- +layout: default +title: Set Up Git (Windows) +description: A quick guide to help you get started with Git +--- + +If you’ve found yourself on this page, we’re assuming you’re brand new to Git and GitHub. This guide will walk you through setting both up, and explain a little about how everything works along the way. If you already have Git experience and just want the short version, read the technical walkthrough instead. + +##First: Download and Install Git + +At the heart of GitHub is an open source version control system (VCS) called Git*. Created by the same dudes that created Linux, Git is responsible for everything GitHub related that happens locally on your computer. + +_*If you don’t already know what Git is, take a crash course._ + +1. Download and install the latest version of msysgit. + + Use the default options for each step. Do not use PuTTY if you are given the option. GitHub only provides support for openssh. + +##Next: Set Up SSH Keys + +We use SSH keys to establish a secure connection between your computer and GitHub. Setting them up is fairly easy, but does involves a number of steps. + +To make sure you generate a brand new key, you need to check if one already exists. First, you need to open Git Bash (not the Windows command line), found in the start menu in the git. + +Open the terminal + +

+Need a quick lesson on Git Bash? +  Code blocks like those on this page are part of a scripting language called Bash. To use Bash scripts, we need to use an application that was installed with msysgit called Git Bash (There is probably an shortcut on your desktop). A line that begins with the dollar sign ($) indicates a line of code you need to type. To enter it, type the text that follows the $, hitting the return key at the end of each line. If you see a line in an example that doesn’t begin with a $ (we’ve made them green in the bootcamp tutorials), that means it is a line of text that Git Bash has output for you to read and/or act upon. In the bootcamp examples, you can roll over the lines of Bash script for an explanation of what they do.

+ + Good to know: There will be times when you type code, hit return, and all you are given is another prompt. Some actions that you execute in Git Bash don’t have any output. Don’t worry, if there is ever a problem with your code, Git Bash will let you know.

+ + Good to know: For security reasons, Git Bash will not display what you type when entering passwords. Just type your password and hit the return key. + + +

+1. Check for SSH keys. Have an existing kepair? You can skip to Step 4. + + First, we need to check for existing ssh keys on your computer: + + 
+	$ cd ~/.sshChecks to see if there is a folder named ".ssh" in you user directory
+
+ +

Does it say "No such file or directory"?

+

No: Go to Step 2
Yes: Skip to Step 3 +

+2. Backup and remove existing SSH keys. + + Since there is already an SSH directory you’ll want to back it up and remove it: + + 
+	$ lsLists all the subdirectories in the current directory
+	config  id_rsa  id_rsa.pub  known_hosts
+	$ mkdir key_backupMakes a folder called "key_backup" in the current directory
+	$ cp id_rsa* key_backupCopies the contents of the id_rsa folder into key_backup folder
+	$ rm id_rsa*Deletes the contents of the id_rsa folder
+
+ +3. Generate a new SSH key. + + To generate a new SSH key, enter the code below. When asked to enter a file in which to save the key, just press enter without typing anything. + + 
+	$ ssh-keygen -t rsa -C "octocat@github.com"Creates a new ssh key using the provided email
+	Generating public/private rsa key pair.
+	Enter file in which to save the key (/c/Users/octocat/.ssh/id_rsa):
+	Enter passphrase (empty for no passphrase):
+	Enter same passphrase again:
+
+ + Which should give you something like this: + + 
+	Your identification has been saved in /c/Users/octocat/.ssh/id_rsa.
+	Your public key has been saved in /c/Users/octocat/.ssh/id_rsa.pub.
+	The key fingerprint is:
+	01:0f:f4:3b:ca:85:d6:17:a1:7d:f0:68:9d:f0:a2:db octocat@github.com
+
+ +4. Add your SSH key to GitHub. + + On the GitHub site _Click “Account Settings”_ > _Click “SSH Public Keys”_ > _Click “Add another public key”_ + + First, open the id_rsa.pub file with a text editor (Notepad will do just fine). This is your SSH key. It’s important you copy your SSH key exactly as it is written without adding any newlines or whitespace. Now paste it into the “Key” field + + Paste your SSH Key + + Hit “Add Key” + +5. Test everything out. + + To make sure everything is working you'll now SSH to GitHub: + + 
+	$ ssh git@github.comAttempts to ssh to github
+
+ + Which should give you this: + + 
+	The authenticity of host 'github.com (207.97.227.239)' can't be established.
+	RSA key fingerprint is 16:27:ac:a5:76:28:2d:36:63:1b:56:4d:eb:df:a6:48.
+	Are you sure you want to continue connecting (yes/no)?
+
+ + Don’t worry, this is supposed to happen. Type “yes”. + + 
+	Warning: Permanently added 'github.com,207.97.227.239' (RSA) to the list of known hosts.
+	ERROR: Hi octocat! You've successfully authenticated, but GitHub does not provide 
shell access
+	Connection to github.com closed.
+
+ +##Then: Set Up Your Info + +Now that you have Git set up and your SSH keys entered in GitHub, it’s time to configure your personal info. + +1. Set your username and email. + + Git tracks who makes each commit by checking the user’s name and email. In addition, we use this info to associate your commits with your GitHub account. To set these, enter the code below, replacing the name and email with your own. The name should be your _actual name_, not your GitHub username. + + 
+	$ git config --global user.name "The Octocat"Sets the name of the user for all git instances on the system
+	$ git config --global user.email "octocat@github.com"Sets the email of the user for all git instances on the system
+
+ +2. Set your GitHub token. + + Some tools connect to GitHub without SSH. To use these tools properly you need to find and configure your API Token. + + On the GitHub site _Click “Account Settings”_ > _Click “Account Admin”_ + + Copy your API token + + In Git Bash, run the following code, using your GitHub username and token in place of the ones shown. + + 
+	$ git config --global github.user octocatSets the GitHub username for all git instances on the system
+	$ git config --global github.token 0123456789abcdef0123456789abcdefSets the GitHub token for all git instances on the system
+
+ + __*Note*__ If you ever change your GitHub password, a new token will be created and will need to be updated. + +##Lastly: Celebrate + +Congratulations, you now have Git and GitHub all set up! What do you want to do next? + +
    +
  1. Set Up Git
    2. +
  2. Create A Repository
    3. +
  3. Fork A Repository
    4. +
  4. Be Social
    5. +
+ \ No newline at end of file -- cgit v1.3.1