Skip to content

Latest commit

 

History

History
129 lines (87 loc) · 5.41 KB

GettingReady.md

File metadata and controls

129 lines (87 loc) · 5.41 KB
Raw

Getting ready

Note: If you are on windows and git was installed as part of another installation (i.e., Visual Studio), please download an up-to-date version and run the installer. Make sure to configure an editor that you are familiar with and that you have a shell that works. If not, ask the trainer before the training starts!

Step 1: Set up your GitHub.com account

For this class, we will use a public account on GitHub.com. We do this for a few reasons:

We don't want you to "practice" in repositories that contain real code We are going to break some things, so we can teach you how to fix them (therefore, refer to the line above)

You can set up your free account by following these steps:

  • Access GitHub.com and click Sign up
  • Choose the free account
  • You will receive a verification email at the address provided
  • Click the link to complete the verification process
  • If you already have an account, verify that you can visit github.com within your organization's network.

GitHub is designed to run on the current versions of all major browsers. Take a look at our list of supported browsers.

Step 2: Install Git

Git is an open source version control application. You will need Git installed for this class.

You may already have Git installed so let's check! Open Terminal if you are on a Mac, or PowerShell if you are on a Windows machine, and type:

git --version

You should see something like this:

console
$ git --version
> git version 2.36.1

In general, we recommend you stay within two minor versions of the latest version of Git. The minor version is the second number in the series x.x.x.

We suggest having version 2.29.2 or more recent if you're using Git for Windows or Git Bash.

Downloading and installing Git If you don't already have Git installed, you can download Git at www.git-scm.com.

If you need additional assistance installing Git, you can find more information in the ProGit chapter on installing Git.

Where is your shell? Now is a good time to create a shortcut to the command-line application you will want to use with Git:

If you are working on Windows, we recommend Git Bash which is installed with the Git package, so that you can follow along with the facilitator who will be using Bash. If you are working on macOS or another Unix-like system, you can use the built-in Terminal application.

Step 3: Try cloning with HTTPS

Open your chosen shell, and type:

git clone https://github.com/wulfland/AccelerateDevOps.git

If the clone is successful you'll see:

$ git clone [https://github.com/wulfland/AccelerateDevOps](https://github.com/wulfland/AccelerateDevOps.git)
> Cloning into 'AccelerateDevOps'...
> remote: Counting objects: 6, done.
> remote: Compressing objects: 100% (2/2), done.
> remote: Total 6 (delta 0), reused 0 (delta 0), pack-reused 0
> Unpacking objects: 100% (6/6), done.

If your clone is unsuccessful, read about authenticating with GitHub from Git. Please note: many corporate networks restrict SSH traffic, so we highly recommend using HTTPS and verifying the clone works before class. Also, if you have two-factor authentication enabled and wish to use HTTPS, you will need to set up a personal access token.

Proxy configuration

If your organization uses a proxy, you will need to configure the proxy settings in Git. Open Git Bash (on Windows) or Terminal (on Mac or *nix) and complete the appropriate steps below:

If your proxy does not require authentication:

git config --global http.proxy https://YOUR.PROXY.SERVER:8080

Replace YOUR.PROXY.SERVER with your proxy's URL.

If your proxy does require authentication:

git config --global http.proxy https://YOUR_PROXY_USERNAME:[email protected]:8080

Replace YOUR_PROXY_USERNAME with the username used to authenticate into your proxy, YOUR_PROXY_PASSWORD with the password used to authenticate into your proxy, and YOUR.PROXY.SERVER with your proxy's URL.

Step 4: Set up your text editor

For this class, we will use a basic text editor to interact with our code. Let's make sure you have one installed and ready to work from the command-line.

Pick your editor You can use almost any text editor, but we have the best success with the following:

Visual Studio Code

  • Notepad++
  • Atom
  • Notepad
  • Vi or Vim
  • Sublime
  • GitPad

If you do not already have a text editor installed, go ahead and download and install one of the above editors now (Visual Studio Code recommended)! You can also configure Visual Studio Code as your default text editor for Git commands using the instructions at docs.github.com.

Your editor on the command-line

After you have installed an editor, confirm you can open it from the command-line.

If installed properly, the following command will open VS Code text editor:

code .

Make the editor the default for git:

git config --global core.editor "code --wait"

For other editors follow the instruction here.