Commit 4e2119c0 authored by Jonathan Chery's avatar Jonathan Chery
Browse files

Updating Week 02

parent 23e2e191
Pipeline #226140 passed with stage
in 42 seconds
......@@ -6,33 +6,38 @@ This week I worked on:
- Installing homebrew on my Mac
- Signing the student agreement
- Exploring the Fab website
- Changing/Updating MKDocs
## Getting familiar Git, Gitlabs, and some Git commands
Due to my past job experience, I am already familiar with Git. However, in the case my memory fails me when working with Git, I often use the [Git Cheat Sheet](docs/files/git_cheatsheet.pdf) to remember some of the commands I need in order to get Git working.
Due to my past job experience, I am already familiar with Git. `Git` is a widely used modern version control system in the world today, according to [Atlassian](https://www.atlassian.com/git/tutorials/what-is-git). However, in the case my memory fails me when working with Git, I often use the [Git Cheat Sheet](../files/git_cheatsheet.pdf) to remember some of the commands I need in order to get Git working. The main commands I use when using Git, Github, or Gitlabs are:
- `git clone <repo>` => Clones the repo onto your local machine.
- `git add <directory/file/all (.)>` => Stages the changes made in the directory or file for the next commit. FYI, adding `.` means add all the files that were changed.
- `git commit -m "<message_goes_here>"` => Adds a message to the commit you're making.
- `git push` => Pushes the directories or files were the changes were made to the Github or Gitlab
This week I spent the time configuring my environment on my MacBook Pro and exploring the tools I will be using:
With Gitlab, there wasn't much of a difference from Github, in regards to usage. However, you can learn more about the difference between Gitlab and Github on [GitLab vs GitHub: Key differences & similarities](https://usersnap.com/blog/gitlab-github/). But, here is a snapshot of the difference.
- Git
- Gitlabs
- Homebrew
![git_difference](../images/week02/git_difference)
## About My Environment
I have a 2020 MacBook Pro running macOS Catalina (I'm long due for an update).
In order for me to make a clone of my repo and have it on my local computer, I needed comfirm I had git installed on my computer. To do so, I needed to type the following command in my terminal:
## Configuring My Environment
![Config](../images/week02/config.jpeg)
`git`
I started off by making sure that my MacBook had `Git` installed. `Git` is a widely used modern version control system in the world today, according to [Atlassian](https://www.atlassian.com/git/tutorials/what-is-git). To insure that Git was installed on my computer, I opened the Terminal application on my MacBook and typed in `git`.
Suddenly,
The result was:
![Git](../images/week02/git.png)
This lovely image of Git commands illustrates that Git is installed on my computer. However, in the case that is wasn't, I would have Googled **How To Install Git on Mac** and I would have found a website similar to this one: [The result of Googling 'How To Install Git On Mac'](https://git-scm.com/book/en/v2/Getting-Started-Installing-Git).
*FYI: I am using a Macbook Pro.*
The list of commands, git commands, comfirm that git is installed on my Macbook. In the case that is wasn't, I would have to go through the documentation of installing Git onto my command. [The result of Googling 'How To Install Git On Mac'](https://git-scm.com/book/en/v2/Getting-Started-Installing-Git).
After installing Git, I needed to configure my Gitlab by having it associated with my computer. To do so, I generated an SSH key on my Macbook Pro and added the key to my GitLab. To Add an SSH Key correctly, I followed the gitlab tutorial: [Generating a new SSH key pair](https://gitlab.fabcloud.org/help/ssh/README#generating-a-new-ssh-key-pair)
----
It wasn't too difficult.
Finally, I needed to install Homebrew on my MacBook. Homebrew is a package manager for macOS (or Linux). More information about Homebrew can be found here: [Homebrew Info](https://brew.sh/)
......
# Table Of Content
1. [Principles and Practices](docs/assignments/week01.md)
2. [Project Management](docs/assignments/week02.md)
\ No newline at end of file
1. [Principles and Practices](/assignments/week01.md)
2. [Project Management](/assignments/week02.md)
\ No newline at end of file
Supports Markdown
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment