Skip to content

Commit 7495fe4

Browse files
Cleaning up setup guide (#178)
* Clean up error doc * Clean up top-level readme, trailing spaces only * OS top level READMEs * Cleanup environment page * Cleanup apt page * Line breaks * Cleanup Homebrew pages * Fixed apt page command structure * Cleanup Git pages * Up through Tree pages * Cleanup Ohmyzsh * Finish ohmyzsh and node pages * Cleanup live-server pages * eslint and folder structure pages cleaned up * Cleaned up vscode pages * Verify pages and finishing touches * Ohmyzsh typos
1 parent 8ae23e6 commit 7495fe4

39 files changed

+1198
-684
lines changed

README.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,7 @@ You do not need to understand what is happening in each step of this process. Ge
88

99
*NOTE: During this process, you will be required to download a few files. For this setup process please **right-click** on links to **open in a new tab** when asked to download and install. This is so you don't lose your place.*
1010

11-
Get started by selecting the appropriate starting point below.
11+
Get started by selecting the appropriate starting point below.
1212

1313
## Software Development Courses
1414

@@ -19,7 +19,7 @@ Begin by selecting your operating system:
1919
- Configure [Windows 10](./system-setup/windows/windows-10.md)
2020
- Configure [Windows 11](./system-setup/windows/windows-11.md)
2121

22-
## Ops and Cybersecurity Courses
22+
## Ops and Cybersecurity Courses
2323

2424
- Configure [all operating systems](./ops-setup/1-network.md)
2525

error/error.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -2,8 +2,8 @@
22

33
Getting a weird error or something unexpected?
44

5-
The frist step is to double-check that you are following the instructions carefully. It's ok to try again.
5+
The first step is to double-check that you are following the instructions carefully. It's ok to try again.
66

7-
If you continue to get an error, check your course syllabus for how to get in touch with your instructor or TAs.
7+
If you continue to get an error, check your course syllabus for how to get in touch with your instructor or TAs.
88

9-
Don't hesitate to reach out! Many issues can be resolved very quickly by those who have been through this process before. Most people need a little assistance with this process at one point or another.
9+
Don't hesitate to reach out! Many issues can be resolved very quickly by those who have been through this process before. Most people need a little assistance with this process at one point or another.

system-setup/1-environment.md

Lines changed: 6 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -1,9 +1,5 @@
11
# Backup Your Terminal/Shell Environment
22

3-
This section will talk about how to update the Terminal's look and feel, as well as how to edit files using the command line editor, `nano`
4-
5-
At the end of this guide, we will add some color to your command line, and your command line will be formatted for development.
6-
73
## Backing up files
84

95
The first thing we'll do is backup your existing terminal setup.
@@ -22,11 +18,13 @@ Make back ups of the files listed below. You may get a `No such file or director
2218

2319
## Windows & Linux Users Only
2420

25-
```bash
26-
sudo apt-get install zsh
27-
```
21+
Run the following command:
22+
23+
- `sudo apt-get install zsh`
24+
25+
After installing, run: `zsh`
2826

29-
After installing, type `zsh`. Zsh will ask you to choose some configuration. We will do this later by installing `oh-my-zsh`. Chose option 0 to create the config file (prevent this message to show again).
27+
Zsh will ask you to choose some configuration. We will do this later by installing `oh-my-zsh`. Chose option 0 to create the config file (prevent this message from showing again).
3028

3129
Now, let's move on to getting our development applications installed.
3230

system-setup/2-apt.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -4,12 +4,12 @@
44

55
For some things on your system, we will be using `apt` to install applications. The first thing we'll want to do is get that up to date with all of the latest versions and information
66

7-
**OPEN YOUR TERMINAL** and let's get started!
8-
9-
1. Type `sudo apt-get update`.
7+
1. Run the command: `sudo apt-get update`
108
- Provide your password, when prompted (***Note:*** *You will not have any visual feedback on your screen as you type. It is protecting your password by not displaying ANYTHING at all to the screen, but it is registering your key strokes.*)
11-
1. Once that is complete, type `sudo apt-get upgrade`. Press `y` when prompted.
12-
1. Once that is done, type `sudo apt autoremove`. This will remove any packages that are no longer needed.
9+
1. Once that is complete, run: `sudo apt-get upgrade`
10+
- Press `y` when prompted.
11+
1. Once that is complete, run: `sudo apt autoremove`
12+
- This will remove any packages that are no longer needed.
1313
1. Install the "Build Essentials" kit with this command: `sudo apt-get install build-essential`
1414

1515
---

system-setup/linux/1-environment.md

Lines changed: 11 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -1,19 +1,17 @@
11
# Backup Your Terminal/Shell Environment
22

3-
This section will talk about how to update the Terminal's look and feel, as well as how to edit files using the command line editor, `nano`
4-
5-
At the end of this guide, we will add some color to your command line, and your command line will be formatted for development.
6-
73
## Backing up files
84

95
The first thing we'll do is backup your existing terminal setup.
106

11-
There are a lot of ways that your terminal can be set up determined by different configuration files.
7+
There are a lot of ways that your terminal can be set up, determined by different configuration files.
128

139
We want to remove the old ways so we can start with a clean slate.
1410

1511
Make back ups of the files listed below. You may get a `No such file or directory` error for some of them. That's ok.
1612

13+
Run these commands:
14+
1715
- `mv ~/.bashrc .bashrc.bak`
1816
- `mv ~/.bash_profile .bash_profile.bak`
1917
- `mv ~/.profile .profile.bak`
@@ -22,11 +20,15 @@ Make back ups of the files listed below. You may get a `No such file or director
2220

2321
## Install Z Shell
2422

25-
```bash
26-
sudo apt-get install zsh
27-
```
23+
Run the following command:
24+
25+
- `sudo apt-get install zsh`
26+
27+
After installing, run the command:
28+
29+
- `zsh`
2830

29-
After installing, type `zsh`. Zsh will ask you to choose some configuration. We will do this later by installing `oh-my-zsh`. Chose option 0 to create the config file (prevent this message to show again).
31+
Zsh will ask you to choose some configuration. We will do this later by installing `oh-my-zsh`. Chose option 0 now to create the config file (prevent this message from showing again).
3032

3133
Now, let's move on to getting our development applications installed.
3234

system-setup/linux/10-vscode.md

Lines changed: 10 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,9 @@
22

33
Now it's time to install VSCode Text Editor, a sophisticated text editor for code, markup, and prose.
44

5-
> **Follow the below instructions in order**, paying attention to any notes specific to Windows or Mac, depending on your operating system.
5+
> **Follow the below instructions in order**, paying attention to any notes specific to your operating system.
6+
7+
---
68

79
## Get Started
810

@@ -11,14 +13,17 @@ Now it's time to install VSCode Text Editor, a sophisticated text editor for cod
1113
- If this window displays during set up, be sure the following boxes are selected
1214
![VSCode](../vscode.png)
1315

14-
### Install Additional VSCode Extensions
16+
---
17+
18+
## Install Required VSCode Extensions
1519

1620
We'll now be adding some functionality to your new code editor by installing a number of extensions.
1721

18-
- You can open VSCode through your terminal using `code .`
22+
- Re-open your terminal and run the command:
23+
- `code .`
1924
- On the bottom left hand side you will see a settings ("gear") icon.
20-
- Click this, then click "Extensions".
21-
- A side-bar will slide out and at the top you can search for the listed extensions below, and click the green 'Install' button for each:
25+
- Click this, then select "Extensions".
26+
- A side-bar will slide out and at the top you can search for the listed extensions below, and click the 'Install' button for each:
2227
- liveserver
2328
- ESLint
2429
- markdownlint

system-setup/linux/11-verify.md

Lines changed: 18 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -1,27 +1,34 @@
11
# Verify Your Setup Part 1
22

3-
> By the time you’ve completed the guide, you should be able to run the following commands in your terminal and see the expected output. Your versions may be slightly different than what is listed here due to recent updates.
3+
> By the time you’ve completed the guide, you should be able to run the following commands in your terminal and see the expected output. Your versions may be slightly higher than what is listed here due to recent updates.
4+
5+
Run these commands and compare them with the expected output.
46

57
- `code --version`
6-
- `1.64.2`
8+
- Expected output: `1.64.2`
79
- `git --version`
8-
- `git version 2.34.1`
10+
- Expected output: `git version 2.34.1`
911
- `node --version`
10-
- `v17.31.1`
12+
- Expected output: `v17.8.0`
1113
- `npm --version`
12-
- `8.3.0`
14+
- Expected output: `8.3.0`
1315
- `eslint --version`
14-
- `v8.1.0`
16+
- Expected output: `v8.1.0`
1517
- `tree --version`
16-
- `tree v2.0.1 (c) 1996 - 2018 ...`
17-
- `git config --list` should contain at least the following:
18+
- Expected output: `tree v2.0.1 (c) 1996 - 2022 ...`
19+
- `git config --list`
20+
- Should contain at least the following:
1821
- `user.name=YOUR NAME`
1922
- `user.email=YOUR EMAIL`
2023
- `core.editor=code --wait`
2124
- `init.defaultbranch=main`
22-
- Type the letter `q` to exit the config screen and return to the previous screen.
25+
- (Type the letter `q` to exit the config screen and return to the previous screen.)
2326
- `code .`
24-
- should open VS Code with your current folder contents
27+
- Should open VS Code with your current folder contents
28+
29+
If any of the above commands do not give you the expected output, get [assistance](../../error/error.md).
30+
31+
---
2532

2633
## Verify Your Setup Part 2
2734

@@ -31,7 +38,7 @@ Run the following command
3138
curl -Ls https://bit.ly/3qMWhbE | bash
3239
```
3340

34-
You should get a successful message. If you do not see `By gum, you've done it!`, look at the output from the steps in part 1 to begin troubleshooting. Get TA assistance as necessary.
41+
You should get a successful message. If instead you see `Something went wrong!`, look at the output carefully, and retry the steps in part 1 to begin troubleshooting. Get [assistance](../../error/error.md) as necessary.
3542

3643
---
3744

system-setup/linux/2-apt.md

Lines changed: 16 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -1,14 +1,22 @@
1-
# Installing and Updating the Linux App Manager
1+
# APT
22

3-
For some things on your system, we will be using `apt` to install applications. The first thing we'll want to do is get that up to date with all of the latest versions and information
3+
For some things on your system, we will be using Advanced Package Tool, referred to as `apt`, to install applications. The first thing we'll want to do is get that up to date with all of the latest versions and information.
44

5-
**OPEN YOUR UBUNTU TERMINAL** and let's get started!
5+
---
6+
7+
## Installing and Updating the Linux App Manager (APT)
68

7-
1. Type `sudo apt-get update`.
8-
- Provide your password, when prompted (***Note:*** *You will not have any visual feedback on your screen as you type. It is protecting your password by not displaying ANYTHING at all to the screen, but it is registering your key strokes.*)
9-
1. Once that is complete, type `sudo apt-get upgrade`. Press `y` when prompted.
10-
1. Once that is done, type `sudo apt autoremove`. This will remove any packages that are no longer needed.
11-
1. Install the "Build Essentials" kit with this command: `sudo apt-get install build-essential`
9+
1. Run the command:
10+
- `sudo apt-get update`
11+
- Provide your password, when prompted (**_Note:_** _You will not have any visual feedback on your screen as you type. It is protecting your password by not displaying ANYTHING at all to the screen, but it is registering your key strokes._)
12+
1. Once that is complete, run:
13+
- `sudo apt-get upgrade`
14+
- Press `y` when prompted.
15+
1. Once that is complete, run:
16+
- `sudo apt autoremove`
17+
- This will remove any packages that are no longer needed.
18+
1. Install the "Build Essentials" kit with this command:
19+
- `sudo apt-get install build-essential`
1220

1321
---
1422

system-setup/linux/3-homebrew.md

Lines changed: 76 additions & 49 deletions
Original file line numberDiff line numberDiff line change
@@ -1,76 +1,103 @@
1-
# Install "Homebrew"
1+
# Homebrew
22

33
Homebrew is a tool that simplifies installing applications on your machine. Think of it like an app store for your computer.
44

55
---
66

77
## Verify if Homebrew is already installed
88

9-
- In your terminal, run: `brew --version`
10-
- _If output is similar to:_ `Homebrew 3.4.11`
11-
- Run: `brew update` to get latest updates
12-
- Move on to [next page](./4-git.md)
13-
- _If output is not similar to the above_, continue with instructions on this page.
9+
**_If this is your first time going through the setup guide on your current machine, skip this "Verify" section and move on to the "Install" section below_**
10+
11+
In your terminal, run:
12+
13+
- `brew --version`
14+
15+
> **IF** the output is similar to:
16+
>
17+
> ```text
18+
> Homebrew 3.4.11
19+
> ```
20+
>
21+
> Run the command:
22+
>
23+
> - `brew update`
24+
>
25+
> to get latest updates, and move on to the [next page](./4-git.md)
26+
>
27+
> ---
28+
> **else if** the output is not similar to the above:
29+
>
30+
> Continue with instructions on this page.
1431
1532
---
1633
17-
In your terminal, enter the following command:
34+
## Install Homebrew
1835
19-
- `/bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/HEAD/install.sh)"`
20-
- You will be prompted several times along the way. Enter your password when prompted, accept all the defaults, say "Yes" if prompted. (**_Note:_** _You will not have any visual feedback on your screen as you type. It is protecting your password by not displaying ANYTHING at all to the screen, but it is registering your key strokes._)
21-
- Once the main installation finishes (could take up to 30 minutes), **look at the output at the bottom of your terminal**. You may see an arrow pointing to "Next Steps" line with 2 commands.
22-
23-
![Homebrew No Next Steps example](../../images/homebrew-next-steps.png)
24-
25-
- Enter those commands, one at a time in your terminal - they should produce no errors, and do not produce success messages.
26-
27-
- Then enter these commands, one at a time in your terminal - they should produce no errors, and do not produce success messages:
28-
- `test -d ~/.linuxbrew && eval $(~/.linuxbrew/bin/brew shellenv)`
29-
- `test -d /home/linuxbrew/.linuxbrew && eval $(/home/linuxbrew/.linuxbrew/bin/brew shellenv)`
30-
31-
Once the installation has completed, **run:**
32-
33-
`brew doctor`
36+
In your terminal, run the following command:
3437
35-
**if** return output is:
36-
37-
```bash
38-
Your system is ready to brew
39-
```
40-
41-
**or** return output is:
42-
43-
```text
44-
Please note that these warnings are just used to help the Homebrew maintainers
45-
with debugging if you file an issue. If everything you use Homebrew for is
46-
working fine: please don't worry or file an issue; just ignore this. Thanks!
47-
```
48-
49-
**then run:**
38+
- `/bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/HEAD/install.sh)"`
5039
51-
`brew update`
40+
You will be prompted several times along the way.
5241
53-
**else if** return output is:
42+
Enter your password when prompted, accept all the defaults, say "Yes" if prompted. (**_Note:_** _You will not have any visual feedback on your screen as you type your password. It is protecting your password by not displaying ANYTHING at all to the screen, but it is registering your key strokes._)
5443
55-
```bash
56-
brew: command not found
57-
```
44+
Once the main installation finishes (could take up to 30 minutes), **look at the output at the bottom of your terminal**. You may see an arrow pointing to **"Next Steps:"** instructions. They would look similar to the image below.
5845
59-
**then** run these commands
46+
![Homebrew No Next Steps example](../../images/homebrew-next-steps.png)
6047
61-
1. `echo 'export BREW_HOME="/home/linuxbrew/.linuxbrew/bin"' >> $HOME/.zshrc`
62-
1. `echo 'export PATH="$PATH:$BREW_HOME"' >> $HOME/.zshrc`
63-
1. `reset`
48+
Run the commands shown in your terminal one at a time - they should produce no errors, and do not produce success messages.
49+
50+
Then run these commands, one at a time in your terminal - they should produce no errors, and do not produce success messages:
51+
52+
- `test -d ~/.linuxbrew && eval $(~/.linuxbrew/bin/brew shellenv)`
53+
- `test -d /home/linuxbrew/.linuxbrew && eval $(/home/linuxbrew/.linuxbrew/bin/brew shellenv)`
54+
55+
Once that step is completed, **run:**
56+
57+
- `brew doctor`
58+
59+
> **IF** the return output is:
60+
>
61+
> ```text
62+
> Your system is ready to brew
63+
> ```
64+
>
65+
> **OR** the return output is:
66+
>
67+
> ```text
68+
> Please note that these warnings are just used to help the Homebrew maintainers with debugging if you file an issue. If everything you use Homebrew for is working fine: please don't worry or file an issue; just ignore this. Thanks!
69+
> ```
70+
>
71+
> **then** run the command:
72+
>
73+
> - `brew update`
74+
>
75+
> ---
76+
> **else if** the return output is:
77+
>
78+
> ```text
79+
> brew: command not found
80+
> ```
81+
>
82+
> **then** run these commands:
83+
>
84+
> - `echo 'export BREW_HOME="/home/linuxbrew/.linuxbrew/bin"' >> $HOME/.zshrc`
85+
> - `echo 'export PATH="$PATH:$BREW_HOME"' >> $HOME/.zshrc`
86+
> - `reset`
87+
>
88+
> and start the sequence over from the `brew doctor` step one more time
89+
90+
**If `brew doctor` still fails to run, [click here](../../error/error.md) and do not continue with the following steps until you have Homebrew properly installed**
6491
65-
> **If `brew update` still fails to run, [click here](../../error/error.md) and do not continue with the following steps until you have Homebrew properly installed**
92+
---
6693
67-
## Install "gcc"
94+
## Install GCC
6895
6996
In order for Homebrew to install other applications, it needs a tool called **gcc** to assist itself.
7097
7198
Run this command in your terminal:
7299
73-
`brew install gcc`
100+
- `brew install gcc`
74101
75102
When that completes, you will be returned to the command prompt and can move on to the next steps.
76103

0 commit comments

Comments
 (0)