├── .gitignore ├── .gitpod.yml ├── .vscode └── settings.json ├── CHANGELOG.md ├── TUTORIAL.md ├── coderoad.yaml ├── freeCodeCamp ├── .bashrc └── test │ ├── .cwd │ └── .next_command └── tutorial.json /.gitignore: -------------------------------------------------------------------------------- 1 | node_modules 2 | .DS_Store 3 | -------------------------------------------------------------------------------- /.gitpod.yml: -------------------------------------------------------------------------------- 1 | image: gitpod/workspace-node-18:2024-01-24-09-19-42 2 | 3 | workspaceLocation: 'project' 4 | checkoutLocation: 'project' 5 | 6 | tasks: 7 | - before: | 8 | sudo touch /workspace/.bash_history 9 | sudo chmod -R 777 /workspace 10 | sudo cp /workspace/project/freeCodeCamp/.bashrc ~/.bashrc 11 | 12 | command: | 13 | sudo rm /workspace/project/CHANGELOG.md 14 | sudo rm /workspace/project/coderoad.yaml 15 | sudo rm /workspace/project/tutorial.json 16 | sudo rm /workspace/project/TUTORIAL.md 17 | exit 18 | 19 | vscode: 20 | extensions: 21 | - CodeRoad.coderoad 22 | -------------------------------------------------------------------------------- /.vscode/settings.json: -------------------------------------------------------------------------------- 1 | { 2 | "breadcrumbs.enabled": false, 3 | "debug.internalConsoleOptions": "neverOpen", 4 | "debug.showInStatusBar": "never", 5 | "editor.acceptSuggestionOnCommitCharacter": false, 6 | "editor.acceptSuggestionOnEnter": "off", 7 | "editor.autoClosingBrackets": "never", 8 | "editor.codeActionsOnSave": { 9 | "source.fixAll": "explicit" 10 | }, 11 | "editor.hover.enabled": false, 12 | "editor.inlineSuggest.enabled": false, 13 | "editor.minimap.enabled": false, 14 | "editor.parameterHints.enabled": false, 15 | "editor.quickSuggestions": { 16 | "other": false, 17 | "comments": false, 18 | "strings": false 19 | }, 20 | "editor.referenceInfos": false, 21 | "editor.snippetSuggestions": "none", 22 | "editor.suggest.statusBar.visible": false, 23 | "editor.suggestOnTriggerCharacters": false, 24 | "editor.tabSize": 2, 25 | "explorer.autoReveal": false, 26 | "explorer.openEditors.visible": 0, 27 | "extensions.autoCheckUpdates": false, 28 | "extensions.ignoreRecommendations": true, 29 | "files.autoSave": "afterDelay", 30 | "files.exclude": { 31 | "**/.git": true, 32 | "**/.svn": true, 33 | "**/.hg": true, 34 | "**/CVS": true, 35 | "**/.DS_Store": true, 36 | ".vscode": true, 37 | ".gitignore": true, 38 | "freeCodeCamp": true, 39 | "learn-bash-by-building-a-boilerplate": true, 40 | ".gitpod.Dockerfile": true, 41 | ".gitpod.yml": true, 42 | "CHANGELOG.md": true, 43 | "coderoad.yaml": true, 44 | "tutorial.json": true, 45 | "TUTORIAL.md": true 46 | }, 47 | "html.autoClosingTags": false, 48 | "npm.fetchOnlinePackageInfo": false, 49 | "task.slowProviderWarning": false, 50 | "terminal.integrated.allowChords": false, 51 | "terminal.integrated.commandsToSkipShell": ["coderoad.enter"], 52 | "terminal.integrated.enableFileLinks": false, 53 | "terminal.integrated.environmentChangesIndicator": "off", 54 | "terminal.integrated.macOptionIsMeta": true, 55 | "terminal.integrated.showExitAlert": false, 56 | "telemetry.enableTelemetry": false, 57 | "update.mode": "none", 58 | "update.showReleaseNotes": false, 59 | "workbench.enableExperiments": false, 60 | "workbench.startupEditor": "none", 61 | "workbench.colorTheme": "Tomorrow Night Blue", 62 | "workbench.colorCustomizations": { 63 | "[Tomorrow Night Blue]": { 64 | "menu.background": "#0a0a23", 65 | "menu.foreground": "#ffffff", 66 | "activityBar.background": "#0a0a23", 67 | "activityBar.foreground": "#ffffff", 68 | "activityBar.activeBorder": "#ffffff", 69 | "activityBar.border": "#2a2a40", 70 | "editorWidget.background": "#0a0a23", 71 | "editorWidget.foreground": "#ffffff", 72 | "sideBar.background": "#1b1b32", 73 | "sideBarTitle.foreground": "#858591", 74 | "sideBar.foreground": "#f5f6f7", 75 | "sideBar.border": "#2a2a40", 76 | "editor.background": "#2a2a40", 77 | "editor.foreground": "#dfdfe2", 78 | "tab.activeForeground": "#ffffff", 79 | "tab.inactiveBackground": "#1b1b32", 80 | "tab.inactiveForeground": "#d0d0d5", 81 | "tab.border": "#2a2a40", 82 | "editorGroupHeader.tabsBackground": "#0a0a23", 83 | "editorIndentGuide.background": "#3b3b4f", 84 | "terminal.background": "#0a0a23", 85 | "terminal.foreground": "#ffffff", 86 | "terminal.ansiBrightGreen": "#ffffff", 87 | "panel.background": "#1b1b32", 88 | "panelTitle.inactiveForeground": "#858591", 89 | "panelTitle.activeBorder": "#f5f6f7" 90 | } 91 | }, 92 | "workbench.iconTheme": null, 93 | "workbench.statusBar.visible": false, 94 | "workbench.tips.enabled": false, 95 | "workbench.tree.renderIndentGuides": "none", 96 | "zenMode.centerLayout": false 97 | } -------------------------------------------------------------------------------- /CHANGELOG.md: -------------------------------------------------------------------------------- 1 | ## Contributing 2 | 3 | Please read the guidelines in the [contributing docs](https://contribute.freecodecamp.org/#/how-to-work-on-tutorials-that-use-coderoad) before contributing. Contributions to this project need to follow the correct workflow. 4 | 5 | # Change Log 6 | 7 | Whenever a new version is created, add the new branch name and the changes here 8 | 9 | ## [v1.0.0] 10 | 11 | - Initial soft release with news article 12 | 13 | ## [v1.0.1] 14 | 15 | - Move setup commands from `coderoad.yaml` to `setup.sh` 16 | - Add creation of `.bash_history` in setup commands so CodeRoad watchers recognize it when the first command is entered 17 | - Fine tune reset commands 18 | 19 | ## [v1.0.2] 20 | 21 | - Restructure commits to use new style. Instead of loading a new test file, and commenting out the old one on each commit, this loads all the tests in the `INIT` commit and uses mocha settings to only run tests in a specific file. The commits now just change the test file that should run. 22 | - There was an issue with the last commit not loading after using the reset button in a tutorial. I added a final commit at end that seems to have resolved it. 23 | - Add hint for [issue on step 160](https://github.com/freeCodeCamp/freeCodeCamp/issues/45521) 24 | 25 | ## [v1.0.3] 26 | 27 | - Moved `touch` and `mkdir` commands to variables: `checkTouch` and `checkMkdir` 28 | - Added a new check and variable for `mv` on `touch` and `mkdir` to account for renaming typos 29 | - changed asserts in those lessons to `assert(checkTouch || checkMV);` or `assert(checkTouch || checkMV);` 30 | 31 | ## [v1.0.4] 32 | 33 | - Remove part of test on 700, 720, 730, and 1450 to similarly (as v1.0.3) account for typos when renaming something 34 | 35 | ## [v2.0.0] 36 | 37 | - Add Gitpod config 38 | -------------------------------------------------------------------------------- /TUTORIAL.md: -------------------------------------------------------------------------------- 1 | # Learn Bash by Building a Boilerplate 2 | 3 | > Welcome to the Introduction to Bash lessons. I know it's scary, but you can do this! 4 | 5 | ## 5. Restart Terminal 6 | 7 | ### 5.1 8 | 9 | **The first thing you need to do is start the terminal.** Do that by clicking the "hamburger" menu at the top left of the screen, going to the "terminal" section, and clicking "new terminal". Once you open a new one, type `echo hello terminal` into the terminal and press enter. 10 | 11 | #### HINTS 12 | 13 | - Capitalization matters 14 | - If the tests don't run automatically, try typing `exit` into the terminal and redoing the instructions 15 | 16 | ## 10. Print Working Directory 17 | 18 | ### 10.1 19 | 20 | What you see in the terminal below is a folder (or directory) on this machine. Type `pwd` into the terminal and press enter to see the path of the folder. `pwd` stands for "print working directory". 21 | 22 | #### HINTS 23 | 24 | - Type `pwd` into the terminal and press enter 25 | - Make sure you are in the `project` folder when you enter the command 26 | - Enter `cd /workspace/project` to get to the `project` folder if you aren't there 27 | 28 | ## 20. List 29 | 30 | ### 20.1 31 | 32 | The output tells you where the folder you are in is located. You are in the `project` folder, which is in the `workspace` folder. Type `ls` into the terminal to see what's in this folder. `ls` stands for "list". 33 | 34 | #### HINTS 35 | 36 | - Type `ls` into the terminal and press enter 37 | - Make sure you are in the `project` folder when you enter the command 38 | - Enter `cd /workspace/project` to get to the `project` folder if you aren't there 39 | 40 | ## 30. Change Directory 41 | 42 | ### 30.1 43 | 44 | The output is showing everything in this folder. There's one folder in here. You can use `cd ` to go into a folder. `cd` stands for "change directory". Change to the `freeCodeCamp` directory. 45 | 46 | #### HINTS 47 | 48 | - Capitalization matters 49 | - Type `cd freeCodeCamp` into the terminal and press enter 50 | - Make sure you start in the `project` folder first 51 | - Enter `cd /workspace/project` to get to the `project` folder if you aren't there 52 | 53 | ## 40. Print Working Directory 54 | 55 | ### 40.1 56 | 57 | You are in the `freecodecamp` folder now. You may have noticed that the prompt changed to include it. Print the working directory of the `freeCodeCamp` folder to see the full path of where you are. 58 | 59 | #### HINTS 60 | 61 | - Use the "print working directory" command 62 | - Type `pwd` into the terminal and press enter 63 | - Make sure you are in the `freeCodeCamp` folder first 64 | - Enter `cd /workspace/project/freeCodeCamp` to get to the `freeCodeCamp` folder if you aren't there 65 | 66 | ## 50. List 67 | 68 | ### 50.1 69 | 70 | You can see the path of the `freeCodeCamp` folder. It's in the `project` folder you were just in. List the contents of the `freeCodeCamp` folder to see what's here. 71 | 72 | #### HINTS 73 | 74 | - Use the "list" command 75 | - Try typing `ls` into the terminal 76 | - Make sure you are in the `freeCodeCamp` folder first 77 | - Enter `cd /workspace/project/freeCodeCamp` to get to the `freeCodeCamp` folder if you aren't there 78 | 79 | ## 60. Change Directory 80 | 81 | ### 60.1 82 | 83 | There's several folders and files here. The folders are blue or green and the files include their extension. Next, change to that `test` directory. 84 | 85 | #### HINTS 86 | 87 | - Use the "change directory" command 88 | - Here's an example: `cd folder-name` 89 | - Try entering `cd test` 90 | - Make sure you enter the command from the `freeCodeCamp` folder 91 | - Enter `cd /workspace/project/freeCodeCamp` to get to the `freeCodeCamp` folder if you aren't there 92 | 93 | ## 70. Print Working Directory 94 | 95 | ### 70.1 96 | 97 | You can see you are in the `test` folder now. It shows `test` in the prompt. Print the full path of this directory. Remember that "folder" and "directory" are the same thing. 98 | 99 | #### HINTS 100 | 101 | - Use the "print working directory" command 102 | - Type `pwd` into the terminal 103 | - Make sure you are in the `test` folder first 104 | - Enter `cd /workspace/project/freeCodeCamp/test` to get to the `test` folder if you aren't there 105 | 106 | ## 80. List 107 | 108 | ### 80.1 109 | 110 | That's the path to the `test` folder, it's in the `freeCodeCamp` folder. **List** the contents of this folder. 111 | 112 | #### HINTS 113 | 114 | - Use the "list" command 115 | - Type `ls` into the terminal 116 | - Make sure you are in the `test` folder first 117 | - Enter `cd /workspace/project/freeCodeCamp/test` to get to the `test` folder if you aren't there 118 | 119 | ## 90. Change Directory 120 | 121 | ### 90.1 122 | 123 | These are all files. There's no more folders to go into here. You can use `cd ..` to go back a folder level. The two dots will take you back one level. Go back to the `freeCodeCamp` folder. 124 | 125 | #### HINTS 126 | 127 | - Use the "change directory" command 128 | - Type `cd ..` into the terminal end press enter 129 | - Type the command from the `test` folder 130 | - Enter `cd /workspace/project/freeCodeCamp/test` to get to the `test` folder if you aren't there 131 | 132 | ## 100. List 133 | 134 | ### 100.1 135 | 136 | `test` got removed from the prompt since you left that folder and you're back in the `freeCodeCamp` folder. List the contents of what's here to remind yourself. 137 | 138 | #### HINTS 139 | 140 | - Use the "list" command 141 | - Type `ls` into the terminal 142 | - Make sure you are in the `freeCodeCamp` folder first 143 | - Enter `cd /workspace/project/freeCodeCamp` to get to the `freeCodeCamp` folder if you aren't there 144 | 145 | ## 110. More 146 | 147 | ### 110.1 148 | 149 | There's the `test` folder you were just in. You can see what's in a file with `more `. Use it to view what's in the `package.json` file. 150 | 151 | #### HINTS 152 | 153 | - Type `more package.json` into the terminal 154 | - Press enter until you have seen the whole file 155 | - Make sure you are in the `freeCodeCamp` folder first 156 | - Enter `cd /workspace/project/freeCodeCamp` to get to the `freeCodeCamp` folder if you aren't there 157 | 158 | ## 120. Clear 159 | 160 | ### 120.1 161 | 162 | It looks like a JSON object. You can empty the terminal with `clear`. The terminal looks a little cluttered, why don't you clear it. 163 | 164 | #### HINTS 165 | 166 | - Commands are case sensitive 167 | - Enter `clear` into the terminal 168 | 169 | ## 130. List 170 | 171 | ### 130.1 172 | 173 | Now you have a fresh screen :smile: List what's in here again. 174 | 175 | #### HINTS 176 | 177 | - Use the "list" command 178 | - Enter `ls` into the terminal 179 | - Make sure you are in the `freeCodeCamp` folder first 180 | - Enter `cd /workspace/project/freeCodeCamp` to get to the `freeCodeCamp` folder if you aren't there 181 | 182 | ## 140. Change Directory 183 | 184 | ### 140.1 185 | 186 | You checked out the `test` folder and the `package.json` file. What next? Why don't you go into that `node_modules` directory. 187 | 188 | #### HINTS 189 | 190 | - Use the "change directory" command 191 | - Here's an example: `cd ` 192 | - Enter `cd node_modules` into the terminal 193 | - Enter `cd /workspace/project/freeCodeCamp` to get back to the `freeCodeCamp` folder and try again 194 | 195 | ## 150. List 196 | 197 | ### 150.1 198 | 199 | Now the prompt includes `node_modules` since that's where you are. List what's in the folder. 200 | 201 | #### HINTS 202 | 203 | - Use the "list" command 204 | - Enter `ls` into the terminal 205 | - Make sure you are in the `node_modules` folder first 206 | - Enter `cd /workspace/project/freeCodeCamp/node_modules` to get to the `node_modules` folder if you aren't there 207 | 208 | ## 160. Long List Format 209 | 210 | ### 160.1 211 | 212 | That's a lot of folders. You can add a **flag** to a command to use it different ways like this: `ls `. List the contents of the `node_modules` folder in "long list format". Do that by adding the `-l` flag to the "list" command. 213 | 214 | #### HINTS 215 | 216 | - Use the "list" command 217 | - Add the `-l` flag to the command 218 | - That's a lowercase letter `l`, not the number `1` 219 | - Enter `ls -l` into the terminal 220 | - Make sure you are in the `node_modules` folder first 221 | - Enter `cd /workspace/project/freeCodeCamp/node_modules` to get to the `node_modules` folder if you aren't there 222 | 223 | ## 170. Change Directory 224 | 225 | ### 170.1 226 | 227 | It is showing more details about each item in here and it's a little easier to read. One of the folders is named `has`, why don't you change into it. 228 | 229 | #### HINTS 230 | 231 | - Use the "change directory" command 232 | - Enter `cd has` into the terminal 233 | - Enter the command from the `node_modules` folder 234 | - Enter `cd /workspace/project/freeCodeCamp/node_modules` to get to the `node_modules` folder if you aren't there 235 | 236 | ## 180. List 237 | 238 | ### 180.1 239 | 240 | You are now in the `has` folder. List its contents. 241 | 242 | #### HINTS 243 | 244 | - Use the "list" command 245 | - Enter `ls` into the terminal 246 | - Enter the command from the `has` folder first 247 | - Enter `cd /workspace/project/freeCodeCamp/node_modules/has` to get to the `has` folder if you aren't there 248 | 249 | ## 181. More 250 | 251 | ### 181.1 252 | 253 | There's a few files and folders here. Can you tell the difference? Take a look at **more** of that `README.md` file. 254 | 255 | #### HINTS 256 | 257 | - Commands and filenames are case sensitive 258 | - Use the "more" command 259 | - Enter `more README.md` into the terminal 260 | - Press "enter" until you have seen the whole file 261 | - Make sure you are in the `has` folder first 262 | - Enter `cd /workspace/project/freeCodeCamp/node_modules/has` to get to the `has` folder if you aren't there 263 | 264 | ## 182. List 265 | 266 | ### 182.1 267 | 268 | Nothing noteworthy in there. You can't see what's in the here anymore, list the contents again. 269 | 270 | #### HINTS 271 | 272 | - Use the "list" command 273 | - Enter `ls` into the terminal 274 | - Make sure you are in the `has` folder first 275 | - Enter `cd /workspace/project/freeCodeCamp/node_modules/has` to get to the `has` folder if you aren't there 276 | 277 | ## 183. More 278 | 279 | ### 183.1 280 | 281 | That one file doesn't appear to have an extension. Strange. Take a look at **more** of the that "license" file that doesn't show an extension. 282 | 283 | #### HINTS 284 | 285 | - Use the "more" command 286 | - Enter `more LICENSE-MIT` into the terminal 287 | - Press "enter" until you have seen the whole file 288 | - Make sure you are in the `has` folder first 289 | - Enter `cd /workspace/project/freeCodeCamp/node_modules/has` to get to the `has` folder if you aren't there 290 | 291 | ## 184. Clear 292 | 293 | ### 184.1 294 | 295 | Pretend you read all that. It looks a little messy in here again so why don't you clear the terminal. 296 | 297 | #### HINTS 298 | 299 | - Use the "clear" command 300 | - Enter `clear` into the terminal 301 | 302 | ## 185. List 303 | 304 | ### 185.1 305 | 306 | Better. Remind yourself what's in here with the list command. 307 | 308 | #### HINTS 309 | 310 | - Use the "list" command 311 | - Enter `ls` into the terminal 312 | - Make sure you are in the `has` folder first 313 | - Enter `cd /workspace/project/freeCodeCamp/node_modules/has` to get to the `has` folder if you aren't there 314 | 315 | ## 190. Change Directory 316 | 317 | ### 190.1 318 | 319 | Go into that `src` directory to see what you can find in there. 320 | 321 | #### HINTS 322 | 323 | - Use the "change directory" command 324 | - Enter `cd src` into the terminal 325 | - Make sure you are in the `has` folder first 326 | - Enter `cd /workspace/project/freeCodeCamp/node_modules/has` to get to the `has` folder if you aren't there 327 | 328 | ## 200. Print Working Directory 329 | 330 | ### 200.1 331 | 332 | View the full path of this folder. 333 | 334 | #### HINTS 335 | 336 | - Use the "print working directory" command 337 | - Enter `pwd` into the terminal 338 | - Make sure you are in the `src` folder 339 | - Enter `cd /workspace/project/freeCodeCamp/node_modules/has/src` to get to the `src` folder if you aren't there 340 | 341 | ## 210. List 342 | 343 | ### 210.1 344 | 345 | Getting deeper still. You can see that each new folder has a `/` in front of it. Take a look at what's in this folder. 346 | 347 | #### HINTS 348 | 349 | - Use the "list" command 350 | - Enter `ls` into the terminal 351 | - Make sure you are in the `src` folder first 352 | - Enter `cd /workspace/project/freeCodeCamp/node_modules/has/src` to get to the `src` folder if you aren't there 353 | 354 | ## 220. More 355 | 356 | ### 220.1 357 | 358 | Only one file here. Show me what's in it with `more`. 359 | 360 | #### HINTS 361 | 362 | - Use the `more` command 363 | - Here's and example: `more filename` 364 | - Enter `more index.js` into the terminal 365 | - Press enter until you've seen all the content 366 | - Make sure you are in the `src` folder first 367 | - Enter `cd /workspace/project/freeCodeCamp/node_modules/has/src` to get to the `src` folder if you aren't there 368 | 369 | ## 230. Change Directory 370 | 371 | ### 230.1 372 | 373 | It's some JavaScript :smile: I think you've fooled around enough. Why don't you navigate out of here. Change back to the `has` directory. 374 | 375 | #### HINTS 376 | 377 | - Use the "change directory" command 378 | - Add `..` after `cd` to go back a folder 379 | - Type `cd ..` into the terminal 380 | - Make sure you are in the `src` folder first 381 | - Enter `cd /workspace/project/freeCodeCamp/node_modules/has/src` to get to the `src` folder if you aren't there 382 | 383 | ## 240. Change Directory 384 | 385 | ### 240.1 386 | 387 | You're getting pretty good. Change back to the `node_modules` directory. 388 | 389 | #### HINTS 390 | 391 | - Use the same `cd` command as the last lesson 392 | - You can press the up arrow to cycle through previous commands 393 | - Type `cd ..` into the terminal 394 | - Make sure you are in the `has` folder first 395 | - Enter `cd /workspace/project/freeCodeCamp/node_modules/has` to get to the `has` folder if you aren't there 396 | 397 | ## 250. Change Directory 398 | 399 | ### 250.1 400 | 401 | You can go back two folders with `cd ../..`. Each set of dots represents another folder level. Go back to the `project` directory from the `node_modules` directory. 402 | 403 | #### HINTS 404 | 405 | - Be sure to go back two folders with one command 406 | - Type `cd ../..` into the terminal from the `node_modules` folder 407 | - Make sure you go from `node_modules` to `project` 408 | - Enter `cd /workspace/project/freeCodeCamp/node_modules` to get to the `node_modules` folder if you aren't there 409 | 410 | ## 260. List 411 | 412 | ### 260.1 413 | 414 | You are back in the `project` folder where you started. List what's in here again. 415 | 416 | #### HINTS 417 | 418 | - Use the "list" command 419 | - Enter `ls` into the terminal 420 | - Make sure you are in the `project` folder first 421 | - Enter `cd /workspace/project` to get to the `project` folder if you aren't there 422 | 423 | ## 270. Clear 424 | 425 | ### 270.1 426 | 427 | That's right. Why don't you get a fresh start by clearing the terminal. 428 | 429 | #### HINTS 430 | 431 | - Use the "clear" command 432 | - Enter `clear` into the terminal 433 | 434 | ## 280. Make Directory 435 | 436 | ### 280.1 437 | 438 | You will be making a website boilerplate. You can make a new folder with `mkdir `. `mkdir` stands for "make directory". Make a `website` directory in this `project` folder. Remember that "directory" and "folder" mean the same thing. 439 | 440 | #### HINTS 441 | 442 | - Enter `mkdir website` into the terminal 443 | - Make sure to make it in the `project` folder 444 | - Don't try to create it with a different method 445 | - Make sure you are in the `project` folder first 446 | - Enter `cd /workspace/project` to get to the `project` folder if you aren't there 447 | 448 | ## 285. List 449 | 450 | ### 285.1 451 | 452 | List what's here to make sure it got created. 453 | 454 | #### HINTS 455 | 456 | - Use the "list" command 457 | - Enter `ls` into the terminal 458 | - Make sure you are in the `project` folder first 459 | - Enter `cd /workspace/project` to get to the `project` folder if you aren't there 460 | - If you used the reset button, you may need to enter the above command to get to the correct folder even if it looks like you're already there 461 | 462 | ## 290. Change Directory 463 | 464 | ### 290.1 465 | 466 | It worked. The website files will be in the new directory. Change to the `website` directory so you can start creating them. 467 | 468 | #### HINTS 469 | 470 | - Use the "change directory" command 471 | - Enter `cd website` into the terminal 472 | - Enter the command from the `project` folder 473 | - Enter `cd /workspace/project` to get to the `project` folder if you aren't there 474 | - If you used the reset button, you may need to enter the above command to get to the correct folder even if it looks like you're already there 475 | 476 | ## 300. List 477 | 478 | ### 300.1 479 | 480 | List the contents of the `website` folder. 481 | 482 | #### HINTS 483 | 484 | - Use the "list" command 485 | - Enter `ls` into the terminal 486 | - Make sure you are in the `website` folder first 487 | - Enter `cd /workspace/project/website` to get to the `website` folder if you aren't there 488 | - If you used the reset button, you may need to enter the above command to get to the correct folder even if it looks like you're already there 489 | 490 | ## 310. Echo 491 | 492 | ### 310.1 493 | 494 | It's brand new, there's nothing in it yet. The `echo` command lets you print anything to the terminal. You used it in the first lesson. Just type what you want to print after it. Use it to print `hello website` to the terminal. 495 | 496 | #### HINTS 497 | 498 | - Here's an example: `echo ` 499 | - Capitalization matters 500 | - Enter `echo hello website` into the terminal 501 | - Make sure you are in the `website` folder first 502 | - Enter `cd /workspace/project/website` to get to the `website` folder if you aren't there 503 | - If you used the reset button, you may need to enter the above command to get to the correct folder even if it looks like you're already there 504 | 505 | ## 320. Touch 506 | 507 | ### 320.1 508 | 509 | Websites usually have an `index.html` file. You can use `touch ` to create a new file. Create `index.html` in the `website` folder. 510 | 511 | #### HINTS 512 | 513 | - Be sure to include the filename and extension 514 | - Don't try to create the file with another method 515 | - Capitalization matters 516 | - Enter `touch index.html` into the terminal 517 | - Make sure you are in the `website` folder first 518 | - Enter `cd /workspace/project/website` to get to the `website` folder if you aren't there 519 | - If you used the reset button, you may need to enter the above command to get to the correct folder even if it looks like you're already there 520 | 521 | ## 330. Touch 522 | 523 | ### 330.1 524 | 525 | They usually have a CSS file as well. Create `styles.css` in the `website` folder using the same method. 526 | 527 | #### HINTS 528 | 529 | - Use the "touch" command 530 | - Here's an example: `touch ` 531 | - Don't try to create the file with another method 532 | - Enter `touch styles.css` in the terminal 533 | - Make sure you are in the `website` folder first 534 | - Enter `cd /workspace/project/website` to get to the `website` folder if you aren't there 535 | - If you used the reset button, you may need to enter the above command to get to the correct folder even if it looks like you're already there 536 | 537 | ## 340. List 538 | 539 | ### 340.1 540 | 541 | List the contents of the `website` folder to make sure they got created. 542 | 543 | #### HINTS 544 | 545 | - Use the `list` command 546 | - Enter `ls` in the terminal 547 | - Make sure you are in the `website` folder first 548 | - Enter `cd /workspace/project/website` to get to the `website` folder if you aren't there 549 | - If you used the reset button, you may need to enter the above command to get to the correct folder even if it looks like you're already there 550 | 551 | ## 350. Touch 552 | 553 | ### 350.1 554 | 555 | There they are. Next is a JavaScript file. Create `index.js` in the `website` folder with the method you have been using. 556 | 557 | #### HINTS 558 | 559 | - Use the "touch" command 560 | - Here's an example: `touch ` 561 | - Don't try to create the file with another method 562 | - Enter `touch index.js` in the terminal 563 | - Make sure you are in the `website` folder first 564 | - Enter `cd /workspace/project/website` to get to the `website` folder if you aren't there 565 | - If you used the reset button, you may need to enter the above command to get to the correct folder even if it looks like you're already there 566 | 567 | ## 360. Touch 568 | 569 | ### 360.1 570 | 571 | You might turn this into a git repository. Create `.gitignore` in the `website` folder with the same method. 572 | 573 | #### HINTS 574 | 575 | - Use the "touch" command 576 | - Here's an example: `touch ` 577 | - Don't try to create the file with another method 578 | - Enter `touch .gitignore` in the terminal 579 | - Make sure you are in the `website` folder first 580 | - Enter `cd /workspace/project/website` to get to the `website` folder if you aren't there 581 | - If you used the reset button, you may need to enter the above command to get to the correct folder even if it looks like you're already there 582 | 583 | ## 370. List 584 | 585 | ### 370.1 586 | 587 | List the contents of the `website` folder to see your new files. 588 | 589 | #### HINTS 590 | 591 | - Use the `list` command 592 | - Make sure you are in the `website` folder 593 | - Enter `ls` in the terminal 594 | - Enter `cd /workspace/project/website` to get to the `website` folder if you aren't there 595 | - If you used the reset button, you may need to enter the above command to get to the correct folder even if it looks like you're already there 596 | 597 | ## 380. Help 598 | 599 | ### 380.1 600 | 601 | There's three files, but where's the `.gitignore` file? I think it's hidden. Most commands have a `--help` flag to show what the command can do. Display the "help" menu for the `ls` command. Here's an example: `command ` 602 | 603 | #### HINTS 604 | 605 | - Use the `list` command with the "help" flag 606 | - You previously used: `ls -l` 607 | - Enter `ls --help` in the terminal 608 | - Make sure you are in the `website` folder first 609 | - Enter `cd /workspace/project/website` to get to the `website` folder if you aren't there 610 | - If you used the reset button, you may need to enter the above command to get to the correct folder even if it looks like you're already there 611 | 612 | ## 390. List All 613 | 614 | ### 390.1 615 | 616 | Scroll through the menu to see the flags that go with `ls`. The flag you are looking for is `--all`, or `-a` for short. List **all** the contents of the `website` folder using the correct flag. 617 | 618 | #### HINTS 619 | 620 | - Use the `list` command with the "all" flag 621 | - Here's an exmple: `command ` 622 | - Enter `ls -a` in the terminal 623 | - Make sure you are in the `website` folder first 624 | - Enter `cd /workspace/project/website` to get to the `website` folder if you aren't there 625 | - If you used the reset button, you may need to enter the above command to get to the correct folder even if it looks like you're already there 626 | 627 | ## 400. Change Directory 628 | 629 | ### 400.1 630 | 631 | There's the hidden file. Do you see it? It didn't display before. It also includes `.` and `..`. You used `cd ..` to go back a folder earlier. Change to the `.` directory. 632 | 633 | #### HINTS 634 | 635 | - Use the "change directory" command 636 | - Enter `cd .` in the terminal 637 | - Make sure you are in the `website` folder first 638 | - Enter `cd /workspace/project/website` to get to the `website` folder if you aren't there 639 | - If you used the reset button, you may need to enter the above command to get to the correct folder even if it looks like you're already there 640 | 641 | ## 410. Touch 642 | 643 | ### 410.1 644 | 645 | You didn't go anywhere. The `.` takes you to the folder you are in, and `..` takes you back, or up, a folder. Websites need some images. Create `background.jpg` in the `website` folder. 646 | 647 | #### HINTS 648 | 649 | - Use the "touch" command 650 | - Here's an example: `touch ` 651 | - Don't try to create the file with another method 652 | - Enter `touch background.jpg` in the terminal 653 | - Make sure you are in the `website` folder first 654 | - Enter `cd /workspace/project/website` to get to the `website` folder if you aren't there 655 | - If you used the reset button, you may need to enter the above command to get to the correct folder even if it looks like you're already there 656 | 657 | ## 420. Touch 658 | 659 | ### 420.1 660 | 661 | Next, add a header image. Create `header.png` in the `website` folder. 662 | 663 | #### HINTS 664 | 665 | - Use the "touch" command 666 | - Here's an example: `touch ` 667 | - Don't try to create the file with another method 668 | - Enter `touch header.png` in the terminal 669 | - Make sure you are in the `website` folder first 670 | - Enter `cd /workspace/project/website` to get to the `website` folder if you aren't there 671 | - If you used the reset button, you may need to enter the above command to get to the correct folder even if it looks like you're already there 672 | 673 | ## 430. Touch 674 | 675 | ### 430.1 676 | 677 | Finally, create `footer.jpeg` in the `website` folder. 678 | 679 | #### HINTS 680 | 681 | - Use the "touch" command 682 | - Here's an example: `touch ` 683 | - Don't try to create the file with another method 684 | - Enter `touch footer.jpeg` in the terminal 685 | - Make sure you are in the `website` folder first 686 | - Enter `cd /workspace/project/website` to get to the `website` folder if you aren't there 687 | - If you used the reset button, you may need to enter the above command to get to the correct folder even if it looks like you're already there 688 | 689 | ## 440. List 690 | 691 | ### 440.1 692 | 693 | Use the **list** command to check out the images you just added. 694 | 695 | #### HINTS 696 | 697 | - Use the "list" command 698 | - Enter `ls` in the terminal 699 | - Make sure you are in the `website` folder first 700 | - Enter `cd /workspace/project/website` to get to the `website` folder if you aren't there 701 | - If you used the reset button, you may need to enter the above command to get to the correct folder even if it looks like you're already there 702 | 703 | ## 450. Touch 704 | 705 | ### 450.1 706 | 707 | Looks like images show up in pink. There's also three fonts to use for the website. The first one is "roboto". Create `roboto.font` in the `website` folder. 708 | 709 | #### HINTS 710 | 711 | - Use the "touch" command 712 | - Don't try to create the file with another method 713 | - Enter `touch roboto.font` in the terminal 714 | - Make sure you are in the `website` folder first 715 | - Enter `cd /workspace/project/website` to get to the `website` folder if you aren't there 716 | - If you used the reset button, you may need to enter the above command to get to the correct folder even if it looks like you're already there 717 | 718 | ## 460. Touch 719 | 720 | ### 460.1 721 | 722 | The next one is "lato". Create `lato.font` in the `website` folder. 723 | 724 | #### HINTS 725 | 726 | - Use the "touch" command 727 | - Don't try to create the file with another method 728 | - Enter `touch lato.font` in the terminal 729 | - Make sure you are in the `website` folder first 730 | - Enter `cd /workspace/project/website` to get to the `website` folder if you aren't there 731 | - If you used the reset button, you may need to enter the above command to get to the correct folder even if it looks like you're already there 732 | 733 | ## 470. Touch 734 | 735 | ### 470.1 736 | 737 | Lastly, create `menlo.font` in the `website` folder. 738 | 739 | #### HINTS 740 | 741 | - Use the "touch" command 742 | - Don't try to create the file with another method 743 | - Enter `touch menlo.font` in the terminal 744 | - Make sure you are in the `website` folder first 745 | - Enter `cd /workspace/project/website` to get to the `website` folder if you aren't there 746 | - If you used the reset button, you may need to enter the above command to get to the correct folder even if it looks like you're already there 747 | 748 | ## 480. List 749 | 750 | ### 480.1 751 | 752 | List the contents of this folder to see your new font files. 753 | 754 | #### HINTS 755 | 756 | - Use the "list" command 757 | - Enter `ls` in the terminal 758 | - Make sure you are in the `website` folder first 759 | - Enter `cd /workspace/project/website` to get to the `website` folder if you aren't there 760 | - If you used the reset button, you may need to enter the above command to get to the correct folder even if it looks like you're already there 761 | 762 | ## 490. Touch 763 | 764 | ### 490.1 765 | 766 | Your three font files are there. There's three icons for the website as well. Create `CodeAlly.svg` in the `website` folder. 767 | 768 | #### HINTS 769 | 770 | - Capitalization matters 771 | - Use the "touch" command 772 | - Don't try to create the file with another method 773 | - Enter `touch CodeAlly.svg` in the terminal 774 | - Make sure you are in the `website` folder first 775 | - Enter `cd /workspace/project/website` to get to the `website` folder if you aren't there 776 | - If you used the reset button, you may need to enter the above command to get to the correct folder even if it looks like you're already there 777 | 778 | ## 500. Touch 779 | 780 | ### 500.1 781 | 782 | Next, create `CodeRoad.svg` in the `website` folder. 783 | 784 | #### HINTS 785 | 786 | - Capitalization matters 787 | - Use the "touch" command 788 | - Don't try to create the file with another method 789 | - Enter `touch CodeRoad.svg` in the terminal 790 | - Make sure you are in the `website` folder first 791 | - Enter `cd /workspace/project/website` to get to the `website` folder if you aren't there 792 | - If you used the reset button, you may need to enter the above command to get to the correct folder even if it looks like you're already there 793 | 794 | ## 510. Touch 795 | 796 | ### 510.1 797 | 798 | Finally, create `freeCodeCamp.svg` in the `website` folder. 799 | 800 | #### HINTS 801 | 802 | - Capitalization matters 803 | - Use the "touch" command 804 | - Don't try to create the file with another method 805 | - Enter `touch freeCodeCamp.svg` in the terminal 806 | - Make sure you are in the `website` folder first 807 | - Enter `cd /workspace/project/website` to get to the `website` folder if you aren't there 808 | - If you used the reset button, you may need to enter the above command to get to the correct folder even if it looks like you're already there 809 | 810 | ## 520. List 811 | 812 | ### 520.1 813 | 814 | Check out the new icons you just added by listing the contents of the folder they are in. 815 | 816 | #### HINTS 817 | 818 | - Use the "list" command 819 | - Enter `ls` in the terminal 820 | - Make sure you are in the `website` folder first 821 | - Enter `cd /workspace/project/website` to get to the `website` folder if you aren't there 822 | - If you used the reset button, you may need to enter the above command to get to the correct folder even if it looks like you're already there 823 | 824 | ## 530. Make Directory 825 | 826 | ### 530.1 827 | 828 | The icons are pink as well. I think the images should go in a separate folder to clean it up a little. Make an `images` directory in the `website` folder to put them in. 829 | 830 | #### HINTS 831 | 832 | - Use the "make directory" command 833 | - It's the `mkdir` command 834 | - Add the folder name after the command 835 | - Here's an example: `mkdir ` 836 | - Enter `mkdir images` into the terminal 837 | - Make sure you are in the `website` folder first 838 | - Enter `cd /workspace/project/website` to get to the `website` folder if you aren't there 839 | - If you used the reset button, you may need to enter the above command to get to the correct folder even if it looks like you're already there 840 | 841 | ## 540. List 842 | 843 | ### 540.1 844 | 845 | List the contents of the `website` folder to make sure your new folder is there. 846 | 847 | #### HINTS 848 | 849 | - Use the "list" command 850 | - Enter `ls` in the terminal 851 | - Make sure you are in the `website` folder first 852 | - Enter `cd /workspace/project/website` to get to the `website` folder if you aren't there 853 | - If you used the reset button, you may need to enter the above command to get to the correct folder even if it looks like you're already there 854 | 855 | ## 550. Copy 856 | 857 | ### 550.1 858 | 859 | There's your new `images` folder. It's blue. You can copy a file with `cp `. `cp` stands for "copy". Copy `background.jpg` to your `images` folder. 860 | 861 | #### HINTS 862 | 863 | - Enter `cp background.jpg images` into the terminal 864 | - Don't try to use a different method to copy it 865 | - Make sure you are in the `website` folder first 866 | - Enter `cd /workspace/project/website` to get to the `website` folder if you aren't there 867 | - If you used the reset button, you may need to enter the above command to get to the correct folder even if it looks like you're already there 868 | 869 | ## 560. Change Directory 870 | 871 | ### 560.1 872 | 873 | Better make sure it worked. Change to the `images` directory. 874 | 875 | #### HINTS 876 | 877 | - Use the "change directory" command 878 | - Enter `cd images` in the terminal 879 | - Make sure you are in the `website` folder first 880 | - Enter `cd /workspace/project/website` to get to the `website` folder if you aren't there 881 | - If you used the reset button, you may need to enter the above command to get to the correct folder even if it looks like you're already there 882 | 883 | ## 570. List 884 | 885 | ### 570.1 886 | 887 | List the contents to see if `background.jpg` is here. 888 | 889 | #### HINTS 890 | 891 | - Use the "list" command 892 | - Make sure you are in the `images` folder 893 | - Enter `ls` in the terminal 894 | - Make sure you are in the `images` folder first 895 | - Enter `cd /workspace/project/website/images` to get to the `images` folder if you aren't there 896 | - If you used the reset button, you may need to enter the above command to get to the correct folder even if it looks like you're already there 897 | 898 | ## 580. Change Directory 899 | 900 | ### 580.1 901 | 902 | There it is. Looks like the copy worked. Change back to the `website` directory so you can copy the other ones. 903 | 904 | #### HINTS 905 | 906 | - Use the "change directory" command 907 | - Add `..` to the command to go back a folder 908 | - Enter `cd ..` in the terminal 909 | - Make sure you are in the `images` folder first 910 | - Enter `cd /workspace/project/website/images` to get to the `images` folder if you aren't there 911 | - If you used the reset button, you may need to enter the above command to get to the correct folder even if it looks like you're already there 912 | 913 | ## 585. List 914 | 915 | ### 585.1 916 | 917 | Remind yourself of the files here by listing the contents. 918 | 919 | #### HINTS 920 | 921 | - Use the "list" command 922 | - Enter `ls` in the terminal 923 | - Make sure you are in the `website` folder first 924 | - Enter `cd /workspace/project/website` to get to the `website` folder if you aren't there 925 | - If you used the reset button, you may need to enter the above command to get to the correct folder even if it looks like you're already there 926 | 927 | ## 590. Remove 928 | 929 | ### 590.1 930 | 931 | You copied the background image to the `images` folder so you don't need the one here anymore. You can remove a file with `rm `. Remove `background.jpg` from the `website` folder. 932 | 933 | #### HINTS 934 | 935 | - Enter `rm background.jpg` in the terminal 936 | - Make sure you are in the `website` folder first 937 | - Enter `cd /workspace/project/website` to get to the `website` folder if you aren't there 938 | - If you used the reset button, you may need to enter the above command to get to the correct folder even if it looks like you're already there 939 | 940 | ## 600. List 941 | 942 | ### 600.1 943 | 944 | List the contents to make sure it's gone. 945 | 946 | #### HINTS 947 | 948 | - Use the "list" command 949 | - Enter `ls` in the terminal 950 | - Make sure you are in the `website` folder first 951 | - Enter `cd /workspace/project/website` to get to the `website` folder if you aren't there 952 | - If you used the reset button, you may need to enter the above command to get to the correct folder even if it looks like you're already there 953 | 954 | ## 610. Copy 955 | 956 | ### 610.1 957 | 958 | Okay, it's gone. Next, copy `header.png` to the `images` folder. 959 | 960 | #### HINTS 961 | 962 | - Here's the example again: `cp ` 963 | - You previously used `cp background.jpg images` 964 | - Don't try to use a different method to copy it 965 | - Enter `cp header.png images` 966 | - Make sure you are in the `website` folder first 967 | - Enter `cd /workspace/project/website` to get to the `website` folder if you aren't there 968 | - If you used the reset button, you may need to enter the above command to get to the correct folder even if it looks like you're already there 969 | 970 | ## 620. Copy 971 | 972 | ### 620.1 973 | 974 | Last, copy the "footer" image to the `images` folder. 975 | 976 | #### HINTS 977 | 978 | - Here's the example again: `cp ` 979 | - You previously used `cp header.png images` 980 | - Don't try to use a different method to copy it 981 | - Enter `cp footer.jpeg images` 982 | - Make sure you are in the `website` folder first 983 | - Enter `cd /workspace/project/website` to get to the `website` folder if you aren't there 984 | - If you used the reset button, you may need to enter the above command to get to the correct folder even if it looks like you're already there 985 | 986 | ## 630. Change Directory 987 | 988 | ### 630.1 989 | 990 | All the images should be copied over. Change to the `images` directory so you can make sure. 991 | 992 | #### HINTS 993 | 994 | - Use the "change directory" command 995 | - Add the path of where you want to go to the command 996 | - Enter `cd images` in the terminal 997 | - Make sure you are in the `website` folder first 998 | - Enter `cd /workspace/project/website` to get to the `website` folder if you aren't there 999 | - If you used the reset button, you may need to enter the above command to get to the correct folder even if it looks like you're already there 1000 | 1001 | ## 640. List 1002 | 1003 | ### 640.1 1004 | 1005 | Check if the images are here by listing the contents. 1006 | 1007 | #### HINTS 1008 | 1009 | - Use the "list" command 1010 | - Enter `ls` in the terminal 1011 | - Make sure you are in the `images` folder first 1012 | - Enter `cd /workspace/project/website/images` to get to the `images` folder if you aren't there 1013 | - If you used the reset button, you may need to enter the above command to get to the correct folder even if it looks like you're already there 1014 | 1015 | ## 650. Change Directory 1016 | 1017 | ### 650.1 1018 | 1019 | They all made it here. Go back to the `website` folder so you can delete the original files. 1020 | 1021 | #### HINTS 1022 | 1023 | - Use the "change directory" command 1024 | - Add `..` to the command to go back a folder 1025 | - Enter `cd ..` in the terminal 1026 | - Make sure you are in the `images` folder first 1027 | - Enter `cd /workspace/project/website/images` to get to the `images` folder if you aren't there 1028 | - If you used the reset button, you may need to enter the above command to get to the correct folder even if it looks like you're already there 1029 | 1030 | ## 660. List 1031 | 1032 | ### 660.1 1033 | 1034 | List the contents to remind yourself of the filenames to delete. 1035 | 1036 | #### HINTS 1037 | 1038 | - Use the "list" command 1039 | - Enter `ls` in the terminal 1040 | - Make sure you are in the `website` folder first 1041 | - Enter `cd /workspace/project/website` to get to the `website` folder if you aren't there 1042 | - If you used the reset button, you may need to enter the above command to get to the correct folder even if it looks like you're already there 1043 | 1044 | ## 670. Remove 1045 | 1046 | ### 670.1 1047 | 1048 | There's two that you don't need anymore. Remove the "header" image file from the `website` folder since you copied to the images folder. 1049 | 1050 | #### HINTS 1051 | 1052 | - Use the "remove" command 1053 | - Here's an example: `rm ` 1054 | - You previously used `rm background.jpg` 1055 | - It's the `header.png` file 1056 | - Enter `rm header.png` in the terminal 1057 | - Don't try to use a different method to delete the file 1058 | - Make sure you are in the `website` folder first 1059 | - Enter `cd /workspace/project/website` to get to the `website` folder if you aren't there 1060 | - If you used the reset button, you may need to enter the above command to get to the correct folder even if it looks like you're already there 1061 | 1062 | ## 680. Remove 1063 | 1064 | ### 680.1 1065 | 1066 | It should be gone. Remove the "footer" image from the `website` folder as well. 1067 | 1068 | #### HINTS 1069 | 1070 | - Use the "remove" command 1071 | - You previously used `rm header.png` 1072 | - The file to remove is `footer.jpg` 1073 | - Don't try to use a different method to delete the file 1074 | - Enter `rm footer.jpeg` in the terminal 1075 | - Make sure you are in the `website` folder first 1076 | - Enter `cd /workspace/project/website` to get to the `website` folder if you aren't there 1077 | - If you used the reset button, you may need to enter the above command to get to the correct folder even if it looks like you're already there 1078 | 1079 | ## 690. List 1080 | 1081 | ### 690.1 1082 | 1083 | List the contents of the `website` folder to check if they are gone. 1084 | 1085 | #### HINTS 1086 | 1087 | - Use the "list" command 1088 | - Enter `ls` in the terminal 1089 | - Make sure you are in the `website` folder first 1090 | - Enter `cd /workspace/project/website` to get to the `website` folder if you aren't there 1091 | - If you used the reset button, you may need to enter the above command to get to the correct folder even if it looks like you're already there 1092 | 1093 | ## 700. Rename 1094 | 1095 | ### 700.1 1096 | 1097 | Looks like they're all deleted. There was a mistake with the extensions for the font files. You can rename them with `mv` like this: `mv `. `mv` stands for "move", it can **rename or move** something. Rename `roboto.font` to `roboto.woff`. 1098 | 1099 | #### HINTS 1100 | 1101 | - Enter `mv roboto.font roboto.woff` 1102 | - Don't try to rename it with other methods 1103 | - Make sure you are in the `website` folder first 1104 | - Enter `cd /workspace/project/website` to get to the `website` folder if you aren't there 1105 | - If you used the reset button, you may need to enter the above command to get to the correct folder even if it looks like you're already there 1106 | 1107 | ## 710. List 1108 | 1109 | ### 710.1 1110 | 1111 | Use "list" to check if it worked. 1112 | 1113 | #### HINTS 1114 | 1115 | - Use the "list" command 1116 | - Enter `ls` in the terminal 1117 | - Make sure you are in the `website` folder first 1118 | - Enter `cd /workspace/project/website` to get to the `website` folder if you aren't there 1119 | - If you used the reset button, you may need to enter the above command to get to the correct folder even if it looks like you're already there 1120 | 1121 | ## 720. Rename 1122 | 1123 | ### 720.1 1124 | 1125 | Do you see the "roboto" font? The rename worked. Next, rename the "lato" font file to `lato.ttf`. 1126 | 1127 | #### HINTS 1128 | 1129 | - Use the "move" command to rename a file 1130 | - Here's the example: `mv ` 1131 | - You previously used: `mv roboto.font roboto.woff` 1132 | - It's the `lato.font` file 1133 | - Don't try to rename it with other methods 1134 | - Enter `mv lato.font lato.ttf` 1135 | - Make sure you are in the `website` folder first 1136 | - Enter `cd /workspace/project/website` to get to the `website` folder if you aren't there 1137 | - If you used the reset button, you may need to enter the above command to get to the correct folder even if it looks like you're already there 1138 | 1139 | ## 730. Rename 1140 | 1141 | ### 730.1 1142 | 1143 | Lastly, rename the "menlo" font to `menlo.otf`. 1144 | 1145 | #### HINTS 1146 | 1147 | - Use the "move" command to rename a file 1148 | - Here's the example: `mv ` 1149 | - You previously used: `mv lato.font lato.ttf` 1150 | - It's the `menlo.font` file 1151 | - Don't try to rename it with other methods 1152 | - Enter `mv menlo.font menlo.otf` 1153 | - Make sure you are in the `website` folder first 1154 | - Enter `cd /workspace/project/website` to get to the `website` folder if you aren't there 1155 | - If you used the reset button, you may need to enter the above command to get to the correct folder even if it looks like you're already there 1156 | 1157 | ## 740. List 1158 | 1159 | ### 740.1 1160 | 1161 | Use the "list" command to make sure those last two got renamed. 1162 | 1163 | #### HINTS 1164 | 1165 | - Use the "list" command 1166 | - Enter `ls` in the terminal 1167 | - Make sure you are in the `website` folder first 1168 | - Enter `cd /workspace/project/website` to get to the `website` folder if you aren't there 1169 | - If you used the reset button, you may need to enter the above command to get to the correct folder even if it looks like you're already there 1170 | 1171 | ## 750. Make Directory 1172 | 1173 | ### 750.1 1174 | 1175 | Take a look at the files to make sure they got renamed. Those font files could be organized into a folder as well. Make a `fonts` directory in the `website` folder to put them in. 1176 | 1177 | #### HINTS 1178 | 1179 | - Use the "make directory" command 1180 | - It's the `mkdir` command 1181 | - Here's an example: `mkdir ` 1182 | - Don't try to create the folder with another method 1183 | - Enter `mkdir fonts` into the terminal 1184 | - Make sure you are in the `website` folder first 1185 | - Enter `cd /workspace/project/website` to get to the `website` folder if you aren't there 1186 | - If you used the reset button, you may need to enter the above command to get to the correct folder even if it looks like you're already there 1187 | 1188 | ## 755. List 1189 | 1190 | ### 755.1 1191 | 1192 | List the contents of the `website` folder to make sure your new folder is there. 1193 | 1194 | #### HINTS 1195 | 1196 | - Use the "list" command 1197 | - Enter `ls` in the terminal 1198 | - Make sure you are in the `website` folder first 1199 | - Enter `cd /workspace/project/website` to get to the `website` folder if you aren't there 1200 | - If you used the reset button, you may need to enter the above command to get to the correct folder even if it looks like you're already there 1201 | 1202 | ## 760. Move 1203 | 1204 | ### 760.1 1205 | 1206 | See it? You renamed the font files with `mv`, you can also move files with it. Move the "roboto" font to the new `fonts` folder. Here's an example: `mv `. 1207 | 1208 | #### HINTS 1209 | 1210 | - Use the "move" command 1211 | - The file to move is `roboto.woff` 1212 | - Don't try to move the file with another method 1213 | - Enter `mv roboto.woff fonts` 1214 | - Make sure you are in the `website` folder first 1215 | - Enter `cd /workspace/project/website` to get to the `website` folder if you aren't there 1216 | - If you used the reset button, you may need to enter the above command to get to the correct folder even if it looks like you're already there 1217 | 1218 | ## 770. Find 1219 | 1220 | ### 770.1 1221 | 1222 | You can use `find` to find things or view a file tree. Enter `find` to view the file tree of the `website` folder to see all the files and folders within it. 1223 | 1224 | #### HINTS 1225 | 1226 | - Use the "find" command 1227 | - Make sure you are in the `website` folder 1228 | - Enter `find` in the terminal 1229 | - Make sure you are in the `website` folder first 1230 | - Enter `cd /workspace/project/website` to get to the `website` folder if you aren't there 1231 | - If you used the reset button, you may need to enter the above command to get to the correct folder even if it looks like you're already there 1232 | 1233 | ## 780. Move 1234 | 1235 | ### 780.1 1236 | 1237 | You can see everything in this `website` folder and its descendant folders. Notice that they all start with `./` to represent this folder. You can see that your font moved to the `fonts` folder. Next, move the "lato" font to the `fonts` folder. 1238 | 1239 | #### HINTS 1240 | 1241 | - Use the "move" command 1242 | - Here's an example: `mv ` 1243 | - The file to move is `lato.ttf` 1244 | - You previously used: `mv roboto.woff fonts` 1245 | - Don't try to move the file with another method 1246 | - Enter `mv lato.ttf fonts` 1247 | - Make sure you are in the `website` folder first 1248 | - Enter `cd /workspace/project/website` to get to the `website` folder if you aren't there 1249 | - If you used the reset button, you may need to enter the above command to get to the correct folder even if it looks like you're already there 1250 | 1251 | ## 790. Move 1252 | 1253 | ### 790.1 1254 | 1255 | There's one more font to move. Move the "menlo" font to the `fonts` folder. 1256 | 1257 | #### HINTS 1258 | 1259 | - Use the "move" command 1260 | - Here's an example: `mv ` 1261 | - The file to move is `menlo.otf` 1262 | - You previously used: `mv lato.ttf fonts` 1263 | - Don't try to move the file with another method 1264 | - Enter `mv menlo.otf fonts` 1265 | - Make sure you are in the `website` folder first 1266 | - Enter `cd /workspace/project/website` to get to the `website` folder if you aren't there 1267 | - If you used the reset button, you may need to enter the above command to get to the correct folder even if it looks like you're already there 1268 | 1269 | ## 800. Find 1270 | 1271 | ### 800.1 1272 | 1273 | Use `find` again to list the whole file tree and make sure those two got moved. 1274 | 1275 | #### HINTS 1276 | 1277 | - Use the "find" command 1278 | - Enter `find` in the terminal 1279 | - Make sure you are in the `website` folder first 1280 | - Enter `cd /workspace/project/website` to get to the `website` folder if you aren't there 1281 | - If you used the reset button, you may need to enter the above command to get to the correct folder even if it looks like you're already there 1282 | 1283 | ## 850. Make Directory 1284 | 1285 | ### 850.1 1286 | 1287 | Yes, you can see them all in the `fonts` folder. Let's organize some more. Make a `client` directory in the `website` folder for the client side files. 1288 | 1289 | #### HINTS 1290 | 1291 | - Use the "make directory" command 1292 | - Here's an example: `mkdir ` 1293 | - Enter `mkdir client` in the terminal 1294 | - Make sure you are in the `website` folder first 1295 | - Enter `cd /workspace/project/website` to get to the `website` folder if you aren't there 1296 | - If you used the reset button, you may need to enter the above command to get to the correct folder even if it looks like you're already there 1297 | 1298 | ## 860. Make Directory 1299 | 1300 | ### 860.1 1301 | 1302 | You can make a folder in that `client` folder from here by adding it to the path like this: `mkdir client/`. Make a `src` directory in the `client` folder from here. 1303 | 1304 | #### HINTS 1305 | 1306 | - Use the "make directory" command 1307 | - Enter `mkdir client/src` from the `website` folder 1308 | - Don't try to create the folder with another method 1309 | - Make sure you are in the `website` folder first 1310 | - Enter `cd /workspace/project/website` to get to the `website` folder if you aren't there 1311 | - If you used the reset button, you may need to enter the above command to get to the correct folder even if it looks like you're already there 1312 | 1313 | ## 870. Move 1314 | 1315 | ### 870.1 1316 | 1317 | You can move files all the way across the system from here with the right path. Move `index.html` to the `client/src` folder from here. 1318 | 1319 | #### HINTS 1320 | 1321 | - Use the "move" command 1322 | - You previously used: `mv menlo.otf fonts` 1323 | - Enter `mv index.html client/src` from the `website` folder 1324 | - Make sure you are in the `website` folder first 1325 | - Enter `cd /workspace/project/website` to get to the `website` folder if you aren't there 1326 | - If you used the reset button, you may need to enter the above command to get to the correct folder even if it looks like you're already there 1327 | 1328 | ## 880. Find 1329 | 1330 | ### 880.1 1331 | 1332 | Use `find` to view the file tree and make sure it moved. 1333 | 1334 | #### HINTS 1335 | 1336 | - Use the "find" command 1337 | - Enter `find` in the terminal 1338 | - Make sure you are in the `website` folder 1339 | - Enter `cd /workspace/project/website` to get to the `website` folder if you aren't there 1340 | - If you used the reset button, you may need to enter the above command to get to the correct folder even if it looks like you're already there 1341 | 1342 | ## 890. Move 1343 | 1344 | ### 890.1 1345 | 1346 | Can you see the `index.html` file in your new `src` folder? Looks like it moved :smile: There's some more files that can go in the `src` folder. Move `index.js` to it from here. 1347 | 1348 | #### HINTS 1349 | 1350 | - Use the "move" command 1351 | - You previously used: `mv index.html client/src` 1352 | - Enter `mv index.js client/src` from the `website` folder 1353 | - Enter `cd /workspace/project/website` to get to the `website` folder if you aren't there 1354 | - If you used the reset button, you may need to enter the above command to get to the correct folder even if it looks like you're already there 1355 | 1356 | ## 900. Move 1357 | 1358 | ### 900.1 1359 | 1360 | Last is the CSS file. Move `styles.css` to the `src` folder. 1361 | 1362 | #### HINTS 1363 | 1364 | - Use the "move" command 1365 | - Don't try to move the file with another method 1366 | - You've used `mv index.js client/src` to move a file 1367 | - Enter `mv styles.css client/src` from the `website` folder 1368 | - Enter `cd /workspace/project/website` to get to the `website` folder if you aren't there 1369 | - If you used the reset button, you may need to enter the above command to get to the correct folder even if it looks like you're already there 1370 | 1371 | ## 910. Find 1372 | 1373 | ### 910.1 1374 | 1375 | Seems like you can do anything right from here. Take another look at the tree with `find`. 1376 | 1377 | #### HINTS 1378 | 1379 | - Use the "find" command 1380 | - Enter `find` in the terminal 1381 | - Make sure you are in the `website` folder first 1382 | - Enter `cd /workspace/project/website` to get to the `website` folder if you aren't there 1383 | - If you used the reset button, you may need to enter the above command to get to the correct folder even if it looks like you're already there 1384 | 1385 | ## 920. Find Subfolder 1386 | 1387 | ### 920.1 1388 | 1389 | Things are looking more organized :smile: You can use `find ` to display the tree of a different folder. View the file tree of the `client` folder from the `website` folder. 1390 | 1391 | #### HINTS 1392 | 1393 | - Use the "find" command 1394 | - Add `client` at the end of the command 1395 | - Enter `find client` in the terminal 1396 | - Make sure you are in the `website` folder first 1397 | - Enter `cd /workspace/project/website` to get to the `website` folder if you aren't there 1398 | - If you used the reset button, you may need to enter the above command to get to the correct folder even if it looks like you're already there 1399 | 1400 | ## 930. Find 1401 | 1402 | ### 930.1 1403 | 1404 | Now you just see what's in the `client` folder. What else can `find` do? View the "help" menu of the `find` command to look around. 1405 | 1406 | #### HINTS 1407 | 1408 | - Use the "find" command with the "help" flag 1409 | - The help flag is: `--help` 1410 | - You previously used `ls --help` 1411 | - Enter `find --help` in the terminal 1412 | - Make sure you are in the `website` folder first 1413 | - Enter `cd /workspace/project/website` to get to the `website` folder if you aren't there 1414 | - If you used the reset button, you may need to enter the above command to get to the correct folder even if it looks like you're already there 1415 | 1416 | ## 940. Find 1417 | 1418 | ### 940.1 1419 | 1420 | The menu isn't very pretty, but there's a `-name` flag in there. You can use it to search for something with `find -name `. Use `find` with the `-name` flag to search for `index.html`. 1421 | 1422 | #### HINTS 1423 | 1424 | - Enter `find -name index.html` in the terminal 1425 | - Make sure you are in the `website` folder first 1426 | - Enter `cd /workspace/project/website` to get to the `website` folder if you aren't there 1427 | - If you used the reset button, you may need to enter the above command to get to the correct folder even if it looks like you're already there 1428 | 1429 | ## 950. Find 1430 | 1431 | ### 950.1 1432 | 1433 | It shows you where that file is. Using the same command, find where the `styles.css` file is. 1434 | 1435 | #### HINTS 1436 | 1437 | - Use the "find" command with the "name" flag and the filename 1438 | - The name flag is: `-name` 1439 | - You previously used `find -name index.html` 1440 | - Enter `find -name style.css` in the terminal 1441 | - Make sure you are in the `website` folder first 1442 | - Enter `cd /workspace/project/website` to get to the `website` folder if you aren't there 1443 | - If you used the reset button, you may need to enter the above command to get to the correct folder even if it looks like you're already there 1444 | 1445 | ## 960. Find 1446 | 1447 | ### 960.1 1448 | 1449 | You can search for folders with it, as well. Using the same command and flag, find the `src` folder. 1450 | 1451 | #### HINTS 1452 | 1453 | - Use the "find" command with the "name" flag 1454 | - The name flag is: `-name` 1455 | - You previously used `find -name index.html` 1456 | - Enter `find -name src` in the terminal 1457 | - Make sure you are in the `website` folder first 1458 | - Enter `cd /workspace/project/website` to get to the `website` folder if you aren't there 1459 | - If you used the reset button, you may need to enter the above command to get to the correct folder even if it looks like you're already there 1460 | 1461 | ## 970. Find 1462 | 1463 | ### 970.1 1464 | 1465 | :smile: View the file tree of the `website` folder to see what else you need to do. 1466 | 1467 | #### HINTS 1468 | 1469 | - Use the "find" command 1470 | - Don't use any flags this time 1471 | - Enter `find` in the terminal 1472 | - Make sure you are in the `website` folder first 1473 | - Enter `cd /workspace/project/website` to get to the `website` folder if you aren't there 1474 | - If you used the reset button, you may need to enter the above command to get to the correct folder even if it looks like you're already there 1475 | 1476 | ## 980. Change Directory 1477 | 1478 | ### 980.1 1479 | 1480 | What's next? More organizing! You should put all the assets in one spot. Change into the `client` folder. 1481 | 1482 | #### HINTS 1483 | 1484 | - Use the "change directory" command 1485 | - Enter `cd client` in the terminal 1486 | - Make sure you are in the `website` folder first 1487 | - Enter `cd /workspace/project/website` to get to the `website` folder if you aren't there 1488 | - If you used the reset button, you may need to enter the above command to get to the correct folder even if it looks like you're already there 1489 | 1490 | ## 990. Make Directory 1491 | 1492 | ### 990.1 1493 | 1494 | Make a new directory named `assets` in the `client` folder. 1495 | 1496 | #### HINTS 1497 | 1498 | - Use the "make directory" command 1499 | - It's the `mkdir` command 1500 | - Here's an example: `mkdir ` 1501 | - You previously used `mkdir client` 1502 | - Enter `mkdir assets` in the terminal 1503 | - Make sure you are in the `client` folder first 1504 | - Enter `cd /workspace/project/website/client` to get to the `client` folder if you aren't there 1505 | - If you used the reset button, you may need to enter the above command to get to the correct folder even if it looks like you're already there 1506 | 1507 | ## 1000. Change Directory 1508 | 1509 | ### 1000.1 1510 | 1511 | Change into the new `assets` folder. 1512 | 1513 | #### HINTS 1514 | 1515 | - Use the "change directory" command 1516 | - It's the `cd` command 1517 | - Enter `cd assets` in the terminal 1518 | - Make sure you are in the `client` folder first 1519 | - Enter `cd /workspace/project/website/client` to get to the `client` folder if you aren't there 1520 | - If you used the reset button, you may need to enter the above command to get to the correct folder even if it looks like you're already there 1521 | 1522 | ## 1010. Make Directory 1523 | 1524 | ### 1010.1 1525 | 1526 | All the images and other assets can go here. Make an `images` directory in the `assets` folder for all the images. 1527 | 1528 | #### HINTS 1529 | 1530 | - Use the "make directory" command 1531 | - It's the `mkdir` command 1532 | - You previously used `mkdir assets` 1533 | - Enter `mkdir images` in the terminal 1534 | - Make sure you are in the `assets` folder first 1535 | - Enter `cd /workspace/project/website/client/assets` to get to the `assets` folder if you aren't there 1536 | - If you used the reset button, you may need to enter the above command to get to the correct folder even if it looks like you're already there 1537 | 1538 | ## 1020. Change Directory 1539 | 1540 | ### 1020.1 1541 | 1542 | Go to your new `images` folder. 1543 | 1544 | #### HINTS 1545 | 1546 | - Use the "change directory" command 1547 | - It's the `cd` command 1548 | - Enter `cd images` in the terminal 1549 | - Make sure you are in the `assets` folder first 1550 | - Enter `cd /workspace/project/website/client/assets` to get to the `assets` folder if you aren't there 1551 | - If you used the reset button, you may need to enter the above command to get to the correct folder even if it looks like you're already there 1552 | 1553 | ## 1030. Touch 1554 | 1555 | ### 1030.1 1556 | 1557 | You want the images here. Create `background.jpg` in this folder. 1558 | 1559 | #### HINTS 1560 | 1561 | - Use the "touch" command 1562 | - You previously used `touch freeCodeCamp.svg` 1563 | - Enter `touch background.jpg` in the terminal 1564 | - Make sure you are in the `images` folder first 1565 | - Enter `cd /workspace/project/website/client/assets/images` to get to the `images` folder if you aren't there 1566 | - If you used the reset button, you may need to enter the above command to get to the correct folder even if it looks like you're already there 1567 | 1568 | ## 1040. Change Directory 1569 | 1570 | ### 1040.1 1571 | 1572 | Wait. You don't need to recreate them. You can just move the other images here. Go back to the `website` folder from here. It's three folder back. 1573 | 1574 | #### HINTS 1575 | 1576 | - Use the "change directory" command 1577 | - You went back two folders with `cd ../..` 1578 | - Enter `cd ../../..` in the terminal 1579 | - Make sure you are in the `images` folder first 1580 | - Enter `cd /workspace/project/website/client/assets/images` to get to the `images` folder if you aren't there 1581 | - If you used the reset button, you may need to enter the above command to get to the correct folder even if it looks like you're already there 1582 | 1583 | ## 1050. Change Directory 1584 | 1585 | ### 1050.1 1586 | 1587 | Now go to where the original images are. Change into the `images` folder. 1588 | 1589 | #### HINTS 1590 | 1591 | - Use the "change directory" command 1592 | - Enter `cd images` in the terminal from the `website` folder 1593 | - Enter `cd /workspace/project/website` to get to the `website` folder if you aren't there 1594 | - If you used the reset button, you may need to enter the above command to get to the correct folder even if it looks like you're already there 1595 | 1596 | ## 1055. List 1597 | 1598 | ### 1055.1 1599 | 1600 | List the contents of the `images` folder to see the files here. 1601 | 1602 | #### HINTS 1603 | 1604 | - Use the "list" command 1605 | - Enter `ls` in the terminal 1606 | - Make sure you are in the `images` folder first 1607 | - Enter `cd /workspace/project/website/images` to get to the `images` folder if you aren't there 1608 | - If you used the reset button, you may need to enter the above command to get to the correct folder even if it looks like you're already there 1609 | 1610 | ## 1060. Move 1611 | 1612 | ### 1060.1 1613 | 1614 | Umm, first I think you should move them back to the website folder. Move `header.png` back to the `website` folder. The destination for the file is `..` 1615 | 1616 | #### HINTS 1617 | 1618 | - Use the "move" command 1619 | - Here's an example: `mv ` 1620 | - Don't try to move the file with another method 1621 | - Enter `mv header.png ..` in the terminal 1622 | - Make sure you are in the `images` folder first 1623 | - Enter `cd /workspace/project/website/images` to get to the `images` folder if you aren't there 1624 | - If you used the reset button, you may need to enter the above command to get to the correct folder even if it looks like you're already there 1625 | 1626 | ## 1065. List 1627 | 1628 | ### 1065.1 1629 | 1630 | List the contents of the `images` folder to see if it's gone. 1631 | 1632 | #### HINTS 1633 | 1634 | - Use the "list" command 1635 | - Enter `ls` in the terminal 1636 | - Make sure you are in the `images` folder first 1637 | - Enter `cd /workspace/project/website/images` to get to the `images` folder if you aren't there 1638 | - If you used the reset button, you may need to enter the above command to get to the correct folder even if it looks like you're already there 1639 | 1640 | ## 1070. Change Directory 1641 | 1642 | ### 1070.1 1643 | 1644 | It's gone. Go back to the `website` folder. 1645 | 1646 | #### HINTS 1647 | 1648 | - Use the "change directory" command 1649 | - Enter `cd ..` in the terminal from the `images` folder 1650 | - Make sure you are in the `images` folder first 1651 | - Enter `cd /workspace/project/website/images` to get to the `images` folder if you aren't there 1652 | - If you used the reset button, you may need to enter the above command to get to the correct folder even if it looks like you're already there 1653 | 1654 | ## 1080. List 1655 | 1656 | ### 1080.1 1657 | 1658 | List what's here. 1659 | 1660 | #### HINTS 1661 | 1662 | - Use the "list" command 1663 | - Enter `ls` in the terminal 1664 | - Make sure you are in the `website` folder first 1665 | - Enter `cd /workspace/project/website` to get to the `website` folder if you aren't there 1666 | - If you used the reset button, you may need to enter the above command to get to the correct folder even if it looks like you're already there 1667 | 1668 | ## 1090. Find 1669 | 1670 | ### 1090.1 1671 | 1672 | There's the file you just moved. Next, you will move it to the `client/assets/images` folder. First, use `find` with the correct flag to search for `images`. 1673 | 1674 | #### HINTS 1675 | 1676 | - Use the "find" command with the "name" flag 1677 | - The name flag is: `-name` 1678 | - Here's an example `find -name ` 1679 | - You previously used `find -name src` 1680 | - Enter `find -name images` in the terminal 1681 | - Make sure you are in the `website` folder first 1682 | - Enter `cd /workspace/project/website` to get to the `website` folder if you aren't there 1683 | - If you used the reset button, you may need to enter the above command to get to the correct folder even if it looks like you're already there 1684 | 1685 | ## 1100. Move 1686 | 1687 | ### 1100.1 1688 | 1689 | There's your two image folders. Move `header.png` to the one with the longer path. Just use it as the destination to do so. 1690 | 1691 | #### HINTS 1692 | 1693 | - Use the "move" command 1694 | - Here's an example: `mv ` 1695 | - The destination you want is `client/assets/images` 1696 | - Don't try to move the file with another method 1697 | - Enter `mv header.png client/assets/images` in the terminal 1698 | - Make sure you are in the `website` folder first 1699 | - Enter `cd /workspace/project/website` to get to the `website` folder if you aren't there 1700 | - If you used the reset button, you may need to enter the above command to get to the correct folder even if it looks like you're already there 1701 | 1702 | ## 1110. Find 1703 | 1704 | ### 1110.1 1705 | 1706 | Use `find` to search for your `header.png` file and make sure it moved. 1707 | 1708 | #### HINTS 1709 | 1710 | - Don't forget the correct flag 1711 | - You want the "name" flag 1712 | - The name flag is: `-name` 1713 | - You previously used `find -name images` 1714 | - Enter `find -name header.png` in the terminal 1715 | - Make sure you are in the `website` folder first 1716 | - Enter `cd /workspace/project/website` to get to the `website` folder if you aren't there 1717 | - If you used the reset button, you may need to enter the above command to get to the correct folder even if it looks like you're already there 1718 | 1719 | ## 1120. Find 1720 | 1721 | ### 1120.1 1722 | 1723 | There it is. Right where you put it. Next, search for your `footer.jpeg` file so you can move that over there. 1724 | 1725 | #### HINTS 1726 | 1727 | - Use the "find" command with the "name" flag 1728 | - The name flag is: `-name` 1729 | - You previously used `find -name header.png` 1730 | - Enter `find -name footer.jpeg` in the terminal 1731 | - Make sure you are in the `website` folder first 1732 | - Enter `cd /workspace/project/website` to get to the `website` folder if you aren't there 1733 | - If you used the reset button, you may need to enter the above command to get to the correct folder even if it looks like you're already there 1734 | 1735 | ## 1130. Move 1736 | 1737 | ### 1130.1 1738 | 1739 | It's in the original `images` folder. You can **use that path** with the move command to move it. Move `footer.jpeg` to the `client/assets/images` folder while in the `website` folder. 1740 | 1741 | #### HINTS 1742 | 1743 | - Use the "move" command 1744 | - You previously used `mv header.png client/assets/images` 1745 | - Make sure you put in the correct two paths 1746 | - The first path is `images/footer.jpeg` 1747 | - The second path is `client/assets/images` 1748 | - Enter `mv images/footer.jpeg client/assets/images` in the terminal 1749 | - Make sure you are in the `website` folder first 1750 | - Enter `cd /workspace/project/website` to get to the `website` folder if you aren't there 1751 | - If you used the reset button, you may need to enter the above command to get to the correct folder even if it looks like you're already there 1752 | 1753 | ## 1135. Find 1754 | 1755 | ### 1135.1 1756 | 1757 | View the file tree of this folder to make sure all your images are over in their new folder. Don't use any flags. 1758 | 1759 | #### HINTS 1760 | 1761 | - Use the "find" command 1762 | - Enter `find` in the terminal 1763 | - Make sure you are in the `website` folder first 1764 | - Enter `cd /workspace/project/website` to get to the `website` folder if you aren't there 1765 | - If you used the reset button, you may need to enter the above command to get to the correct folder even if it looks like you're already there 1766 | 1767 | ## 1150. Remove Directory 1768 | 1769 | ### 1150.1 1770 | 1771 | You don't need the old `images` folder anymore. You can use `rmdir ` to remove a folder. `rmdir` stands for "remove directory". Try to remove the `images` folder with `rmdir`. Make sure it's the one in the `website` folder. 1772 | 1773 | #### HINTS 1774 | 1775 | - Enter `rmdir images` into the terminal 1776 | - Make sure you are in the `website` folder first 1777 | - Enter `cd /workspace/project/website` to get to the `website` folder if you aren't there 1778 | - If you used the reset button, you may need to enter the above command to get to the correct folder even if it looks like you're already there 1779 | 1780 | ## 1170. Remove 1781 | 1782 | ### 1170.1 1783 | 1784 | Directory not empty? Oh yeah, there's still the background image in there. Remove the background image file in the `images` folder from here. Make sure it's the one in the `website/images` folder. 1785 | 1786 | #### HINTS 1787 | 1788 | - Use the `rm` command 1789 | - Here's an example: `rm ` 1790 | - The file path you want is `images/background.jpg` 1791 | - Enter `rm images/background.jpg` in the terminal 1792 | - Make sure you are in the `website` folder first 1793 | - Enter `cd /workspace/project/website` to get to the `website` folder if you aren't there 1794 | - If you used the reset button, you may need to enter the above command to get to the correct folder even if it looks like you're already there 1795 | 1796 | ## 1190. Remove Directory 1797 | 1798 | ### 1190.1 1799 | 1800 | Try to remove the `images` folder again with `rmdir`. Make sure it's the one in the `website` folder. 1801 | 1802 | #### HINTS 1803 | 1804 | - Use the "remove directory" command 1805 | - Enter `rmdir images` in the terminal 1806 | - Make sure you are in the `website` folder first 1807 | - Enter `cd /workspace/project/website` to get to the `website` folder if you aren't there 1808 | - If you used the reset button, you may need to enter the above command to get to the correct folder even if it looks like you're already there 1809 | 1810 | ## 1195. List 1811 | 1812 | ### 1195.1 1813 | 1814 | I think it worked this time. List the contents to find out. 1815 | 1816 | #### HINTS 1817 | 1818 | - Use the "list" command 1819 | - Enter `ls` in the terminal 1820 | - Make sure you are in the `website` folder first 1821 | - Enter `cd /workspace/project/website` to get to the `website` folder if you aren't there 1822 | - If you used the reset button, you may need to enter the above command to get to the correct folder even if it looks like you're already there 1823 | 1824 | ## 1200. Make Directory 1825 | 1826 | ### 1200.1 1827 | 1828 | It worked, the `images` folder is gone. Make a new `icons` folder in your `assets` folder while in the `website` folder. 1829 | 1830 | #### HINTS 1831 | 1832 | - Use the `mkdir` command 1833 | - Your `assets` folder is in the `client` folder 1834 | - Don't try to create the directory with another method 1835 | - Enter `mkdir client/assets/icons` into the terminal 1836 | - Make sure you are in the `website` folder first 1837 | - Enter `cd /workspace/project/website` to get to the `website` folder if you aren't there 1838 | - If you used the reset button, you may need to enter the above command to get to the correct folder even if it looks like you're already there 1839 | 1840 | ## 1210. Move 1841 | 1842 | ### 1210.1 1843 | 1844 | Move the `CodeAlly.svg` file to your new `icons` folder. 1845 | 1846 | #### HINTS 1847 | 1848 | - Use the "move" command 1849 | - Here's a tip: `mv CodeAlly.svg ` 1850 | - The destination path is `client/assets/icons` 1851 | - Enter `mv CodeAlly.svg client/assets/icons` into the terminal 1852 | - Make sure you are in the `website` folder first 1853 | - Enter `cd /workspace/project/website` to get to the `website` folder if you aren't there 1854 | - If you used the reset button, you may need to enter the above command to get to the correct folder even if it looks like you're already there 1855 | 1856 | ## 1215. Find 1857 | 1858 | ### 1215.1 1859 | 1860 | View the file tree of the `website` folder and make sure it moved. 1861 | 1862 | #### HINTS 1863 | 1864 | - Use the "find" command 1865 | - Enter `find` in the terminal 1866 | - Make sure you are in the `website` folder first 1867 | - Enter `cd /workspace/project/website` to get to the `website` folder if you aren't there 1868 | - If you used the reset button, you may need to enter the above command to get to the correct folder even if it looks like you're already there 1869 | 1870 | ## 1220. Move 1871 | 1872 | ### 1220.1 1873 | 1874 | Verify that the file moved to the `icons` folder. Next, move the "CodeRoad" file to your `icons` folder. 1875 | 1876 | #### HINTS 1877 | 1878 | - Use the "move" command 1879 | - The filename is `CodeRoad.svg` 1880 | - Here's a tip: `mv CodeRoad.svg ` 1881 | - Enter `mv CodeRoad.svg client/assets/icons` into the terminal 1882 | - Make sure you are in the `website` folder first 1883 | - Enter `cd /workspace/project/website` to get to the `website` folder if you aren't there 1884 | - If you used the reset button, you may need to enter the above command to get to the correct folder even if it looks like you're already there 1885 | 1886 | ## 1230. Move 1887 | 1888 | ### 1230.1 1889 | 1890 | Lastly, move the "freeCodeCamp" file to your `icons` folder. 1891 | 1892 | #### HINTS 1893 | 1894 | - Use the "move" command 1895 | - Here's a tip: `mv freeCodeCamp.svg ` 1896 | - The path is `client/assets/icons` 1897 | - Enter `mv freeCodeCamp.svg client/assets/icons` into the terminal 1898 | - Make sure you are in the `website` folder first 1899 | - Enter `cd /workspace/project/website` to get to the `website` folder if you aren't there 1900 | - If you used the reset button, you may need to enter the above command to get to the correct folder even if it looks like you're already there 1901 | 1902 | ## 1240. Find 1903 | 1904 | ### 1240.1 1905 | 1906 | View the file tree and make sure the files moved. 1907 | 1908 | #### HINTS 1909 | 1910 | - Use the "find" command 1911 | - Enter `find` in the terminal 1912 | - Make sure you are in the `website` folder first 1913 | - Enter `cd /workspace/project/website` to get to the `website` folder if you aren't there 1914 | - If you used the reset button, you may need to enter the above command to get to the correct folder even if it looks like you're already there 1915 | 1916 | ## 1250. Make Directory 1917 | 1918 | ### 1250.1 1919 | 1920 | This looks much better. The three icons are now in the `icons` folder. Make a `fonts` folder in your `assets` folder from here for all the font files. 1921 | 1922 | #### HINTS 1923 | 1924 | - Use the `mkdir` command 1925 | - Put the `fonts` folder in the `client/assets` folder 1926 | - Enter `mkdir client/assets/fonts` in the terminal 1927 | - Make sure you are in the `website` folder first 1928 | - Enter `cd /workspace/project/website` to get to the `website` folder if you aren't there 1929 | - If you used the reset button, you may need to enter the above command to get to the correct folder even if it looks like you're already there 1930 | 1931 | ## 1260. Touch 1932 | 1933 | ### 1260.1 1934 | 1935 | Turns out you want some different fonts for the website. From here, create `roboto-bold.woff` in your new `fonts` folder. You can put the path in front of the filename of where you want it to go. 1936 | 1937 | #### HINTS 1938 | 1939 | - Use the "touch" command 1940 | - Here's an example: `touch ` 1941 | - The file needs to be created in the `client/assets/fonts` folder 1942 | - Enter `touch client/assets/fonts/roboto-bold.woff` in the terminal 1943 | - Make sure you are in the `website` folder first 1944 | - Enter `cd /workspace/project/website` to get to the `website` folder if you aren't there 1945 | - If you used the reset button, you may need to enter the above command to get to the correct folder even if it looks like you're already there 1946 | 1947 | ## 1270. Touch 1948 | 1949 | ### 1270.1 1950 | 1951 | Next, create `roboto-light.woff` in your new `fonts` folder from here. 1952 | 1953 | #### HINTS 1954 | 1955 | - Use the "touch" command 1956 | - Here's an example: `touch ` 1957 | - Put the file in the `client/assets/fonts` folder 1958 | - You previously used: `touch client/assets/fonts/roboto-bold.woff` 1959 | - Enter `touch client/assets/fonts/roboto-light.woff` in the terminal 1960 | - Make sure you are in the `website` folder first 1961 | - Enter `cd /workspace/project/website` to get to the `website` folder if you aren't there 1962 | - If you used the reset button, you may need to enter the above command to get to the correct folder even if it looks like you're already there 1963 | 1964 | ## 1275. Find 1965 | 1966 | ### 1275.1 1967 | 1968 | View the file tree of the `client/assets/fonts` folder from here to see if your new files are there. 1969 | 1970 | #### HINTS 1971 | 1972 | - Use the "find" command with the folder path you want to see 1973 | - Here's an example: `find ` 1974 | - Enter `find client/assets/fonts` in the terminal 1975 | - Make sure you are in the `website` folder first 1976 | - Enter `cd /workspace/project/website` to get to the `website` folder if you aren't there 1977 | - If you used the reset button, you may need to enter the above command to get to the correct folder even if it looks like you're already there 1978 | 1979 | ## 1280. Touch 1980 | 1981 | ### 1280.1 1982 | 1983 | Two more fonts to go. Create `lato-bold.ttf` in the new `fonts` folder from here. 1984 | 1985 | #### HINTS 1986 | 1987 | - Use the "touch" command 1988 | - Here's an example: `touch ` 1989 | - Put the file in the `client/assets/fonts` folder 1990 | - You previously used: `touch client/assets/fonts/roboto-light.woff` 1991 | - Enter `touch client/assets/fonts/lato-bold.ttf` in the terminal 1992 | - Make sure you are in the `website` folder first 1993 | - Enter `cd /workspace/project/website` to get to the `website` folder if you aren't there 1994 | - If you used the reset button, you may need to enter the above command to get to the correct folder even if it looks like you're already there 1995 | 1996 | ## 1290. Touch 1997 | 1998 | ### 1290.1 1999 | 2000 | Lastly, create `lato-light.ttf` in your new `fonts` folder from here. 2001 | 2002 | #### HINTS 2003 | 2004 | - Use the "touch" command 2005 | - Here's an example: `touch ` 2006 | - You previously used: `touch client/assets/fonts/lato-bold.ttf` 2007 | - Enter `touch client/assets/fonts/lato-light.ttf` in the terminal 2008 | - Make sure you are in the `website` folder first 2009 | - Enter `cd /workspace/project/website` to get to the `website` folder if you aren't there 2010 | - If you used the reset button, you may need to enter the above command to get to the correct folder even if it looks like you're already there 2011 | 2012 | ## 1300. Find 2013 | 2014 | ### 1300.1 2015 | 2016 | View your file tree and make sure the files are there. 2017 | 2018 | #### HINTS 2019 | 2020 | - Use the "find" command 2021 | - Enter `find` in the terminal 2022 | - Make sure you are in the `website` folder first 2023 | - Enter `cd /workspace/project/website` to get to the `website` folder if you aren't there 2024 | - If you used the reset button, you may need to enter the above command to get to the correct folder even if it looks like you're already there 2025 | 2026 | ## 1310. Remove Help 2027 | 2028 | ### 1310.1 2029 | 2030 | Things are looking more organized :smile: The new fonts are there. Now you can remove the old `fonts` folder and everything in it. You can't do that with `rmdir` since it's not empty. View the "help" menu of the `rm` command to see if you can find anything. 2031 | 2032 | #### HINTS 2033 | 2034 | - Use the "remove" command with the "help" flag 2035 | - The "help" flag is `--help` 2036 | - Enter `rm --help` into the terminal 2037 | - Make sure you are in the `website` folder first 2038 | - Enter `cd /workspace/project/website` to get to the `website` folder if you aren't there 2039 | - If you used the reset button, you may need to enter the above command to get to the correct folder even if it looks like you're already there 2040 | 2041 | ## 1315. Remove Recursively 2042 | 2043 | ### 1315.1 2044 | 2045 | There's a `-r` flag that says, `remove directories and their contents recursively`. That will remove the folder and everything in it. Use the "remove" command with that flag to remove the `fonts` folder. Make sure it's the one in the `website` folder. Be careful not to remove the wrong folder. 2046 | 2047 | #### HINTS 2048 | 2049 | - The "remove" command is `rm` 2050 | - The flag you want is `-r` 2051 | - Here's an example: `rm -r ` 2052 | - Enter `rm -r fonts` in the terminal 2053 | - Make sure you are in the `website` folder first 2054 | - Enter `cd /workspace/project/website` to get to the `website` folder if you aren't there 2055 | 2056 | ## 1320. List 2057 | 2058 | ### 1320.1 2059 | 2060 | List what's here to see if it's gone. 2061 | 2062 | #### HINTS 2063 | 2064 | - Use the "list" command 2065 | - Enter `ls` in the terminal 2066 | - Make sure you are in the `website` folder first 2067 | - Enter `cd /workspace/project/website` to get to the `website` folder if you aren't there 2068 | - If you used the reset button, you may need to enter the above command to get to the correct folder even if it looks like you're already there 2069 | 2070 | ## 1330. Touch 2071 | 2072 | ### 1330.1 2073 | 2074 | Looks like it’s gone. Surely, it went to the trash can right? No, it’s just gone. You should **be very careful when recursively removing files** like that. It will delete everything, and can destroy your operating system. There's a few more files for the boilerplate. Create `package.json` in the `website` folder. 2075 | 2076 | #### HINTS 2077 | 2078 | - Use the "touch" command 2079 | - Enter `touch package.json` in the terminal 2080 | - Make sure you are in the `website` folder first 2081 | - Enter `cd /workspace/project/website` to get to the `website` folder if you aren't there 2082 | - If you used the reset button, you may need to enter the above command to get to the correct folder even if it looks like you're already there 2083 | 2084 | ## 1340. Touch 2085 | 2086 | ### 1340.1 2087 | 2088 | Next, create `server.js` in the `website` folder. 2089 | 2090 | #### HINTS 2091 | 2092 | - Use the "touch" command 2093 | - Enter `touch server.js` in the terminal 2094 | - Make sure you are in the `website` folder first 2095 | - Enter `cd /workspace/project/website` to get to the `website` folder if you aren't there 2096 | - If you used the reset button, you may need to enter the above command to get to the correct folder even if it looks like you're already there 2097 | 2098 | ## 1350. Touch 2099 | 2100 | ### 1350.1 2101 | 2102 | Lastly, create `README.md` in the `website` folder. 2103 | 2104 | #### HINTS 2105 | 2106 | - Use the "touch" command 2107 | - Capitalization matters 2108 | - Enter `touch README.md` in the terminal 2109 | - Make sure you are in the `website` folder first 2110 | - Enter `cd /workspace/project/website` to get to the `website` folder if you aren't there 2111 | - If you used the reset button, you may need to enter the above command to get to the correct folder even if it looks like you're already there 2112 | 2113 | ## 1360. List 2114 | 2115 | ### 1360.1 2116 | 2117 | List the content of this folder to make sure your new files are there. 2118 | 2119 | #### HINTS 2120 | 2121 | - Use the "list" command 2122 | - Enter `ls` in the terminal 2123 | - Make sure you are in the `website` folder first 2124 | - Enter `cd /workspace/project/website` to get to the `website` folder if you aren't there 2125 | - If you used the reset button, you may need to enter the above command to get to the correct folder even if it looks like you're already there 2126 | 2127 | ## 1370. Echo 2128 | 2129 | ### 1370.1 2130 | 2131 | The boilerplate is complete. Use `echo` to print `Yay!` to the terminal. 2132 | 2133 | #### HINTS 2134 | 2135 | - Use the "echo" command 2136 | - Here's an example: `echo ` 2137 | - Enter `echo Yay!` in the terminal 2138 | - Make sure you are in the `website` folder first 2139 | - Enter `cd /workspace/project/website` to get to the `website` folder if you aren't there 2140 | - If you used the reset button, you may need to enter the above command to get to the correct folder even if it looks like you're already there 2141 | 2142 | ## 1380. Echo 2143 | 2144 | ### 1380.1 2145 | 2146 | Print `I finished the boilerplate!` to the terminal. 2147 | 2148 | #### HINTS 2149 | 2150 | - Use the "echo" command 2151 | - Enter `echo I finished the boilerplate!` in the terminal 2152 | - Make sure you are in the `website` folder first 2153 | - Enter `cd /workspace/project/website` to get to the `website` folder if you aren't there 2154 | - If you used the reset button, you may need to enter the above command to get to the correct folder even if it looks like you're already there 2155 | 2156 | ## 1390. Echo 2157 | 2158 | ### 1390.1 2159 | 2160 | Print `one more thing...` to the terminal 2161 | 2162 | #### HINTS 2163 | 2164 | - Use the "echo" command 2165 | - Enter `echo one more thing...` in the terminal 2166 | - Make sure you are in the `website` folder first 2167 | - Enter `cd /workspace/project/website` to get to the `website` folder if you aren't there 2168 | - If you used the reset button, you may need to enter the above command to get to the correct folder even if it looks like you're already there 2169 | 2170 | ## 1400. Echo to File 2171 | 2172 | ### 1400.1 2173 | 2174 | You can print to a file instead of the terminal with `echo text >> filename`. Use it to print `I made this boilerplate` to your `README.md` file. 2175 | 2176 | #### HINTS 2177 | 2178 | - Use the "echo" command 2179 | - Enter `echo I made this boilerplate >> README.md` in the terminal 2180 | - Make sure you are in the `website` folder first 2181 | - Enter `cd /workspace/project/website` to get to the `website` folder if you aren't there 2182 | - If you used the reset button, you may need to enter the above command to get to the correct folder even if it looks like you're already there 2183 | 2184 | ## 1405. More 2185 | 2186 | ### 1405.1 2187 | 2188 | Use `more` to view your `README.md` file. 2189 | 2190 | #### HINTS 2191 | 2192 | - Use the "more" command 2193 | - Enter `more README.md` in the terminal 2194 | - Make sure you are in the `website` folder first 2195 | - Enter `cd /workspace/project/website` to get to the `website` folder if you aren't there 2196 | - If you used the reset button, you may need to enter the above command to get to the correct folder even if it looks like you're already there 2197 | 2198 | ## 1410. Echo to File 2199 | 2200 | ### 1410.1 2201 | 2202 | Now that line is in the file. Add `from the command line` to your `README.md` file with the `echo` command and the same method. 2203 | 2204 | #### HINTS 2205 | 2206 | - Use the "echo" command with `>>` to add text to a file 2207 | - Here's an example: `echo >> ` 2208 | - You previously used: `echo I made this boilerplate >> README.md` 2209 | - Enter `echo from the command line >> README.md` in the terminal 2210 | - Make sure you are in the `website` folder first 2211 | - Enter `cd /workspace/project/website` to get to the `website` folder if you aren't there 2212 | - If you used the reset button, you may need to enter the above command to get to the correct folder even if it looks like you're already there 2213 | 2214 | ## 1415. More 2215 | 2216 | ### 1415.1 2217 | 2218 | Use `more` to view the "readme" file again. 2219 | 2220 | #### HINTS 2221 | 2222 | - Use the "more" command 2223 | - Enter `more README.md` in the terminal 2224 | - Make sure you are in the `website` folder first 2225 | - Enter `cd /workspace/project/website` to get to the `website` folder if you aren't there 2226 | - If you used the reset button, you may need to enter the above command to get to the correct folder even if it looks like you're already there 2227 | 2228 | ## 1420. Echo to File 2229 | 2230 | ### 1420.1 2231 | 2232 | Now the file has two lines. Add `for the freeCodeCamp bash lessons` to your "readme" file with the `echo` command like you did before. 2233 | 2234 | #### HINTS 2235 | 2236 | - Use the "echo" command with `>>` to add text to a file 2237 | - Here's an example: `echo >> ` 2238 | - You previously used: `echo from the command line >> README.md` in the terminal 2239 | - Enter `echo for the freeCodeCamp bash lessons >> README.md` in the terminal 2240 | - Make sure you are in the `website` folder first 2241 | - Enter `cd /workspace/project/website` to get to the `website` folder if you aren't there 2242 | - If you used the reset button, you may need to enter the above command to get to the correct folder even if it looks like you're already there 2243 | 2244 | ## 1430. More 2245 | 2246 | ### 1430.1 2247 | 2248 | View your "readme" file again like you did before. 2249 | 2250 | #### HINTS 2251 | 2252 | - Use the "more" command 2253 | - Enter `more README.md` in the terminal 2254 | - Make sure you are in the `website` folder first 2255 | - Enter `cd /workspace/project/website` to get to the `website` folder if you aren't there 2256 | - If you used the reset button, you may need to enter the above command to get to the correct folder even if it looks like you're already there 2257 | 2258 | ## 1440. Change Directory 2259 | 2260 | ### 1440.1 2261 | 2262 | :smile: Change to the `project` folder. 2263 | 2264 | #### HINTS 2265 | 2266 | - Use the "change directory" command 2267 | - Enter `cd ..` in the terminal 2268 | - Make sure you are in the `website` folder first 2269 | - Enter `cd /workspace/project/website` to get to the `website` folder if you aren't there 2270 | - If you used the reset button, you may need to enter the above command to get to the correct folder even if it looks like you're already there 2271 | 2272 | ## 1445. List 2273 | 2274 | ### 1445.1 2275 | 2276 | You are back where you started. List what's here. 2277 | 2278 | #### HINTS 2279 | 2280 | - Use the "list" command 2281 | - Enter `ls` in the terminal 2282 | - Make sure you are in the `project` folder first 2283 | - Enter `cd /workspace/project` to get to the `project` folder if you aren't there 2284 | - If you used the reset button, you may need to enter the above command to get to the correct folder even if it looks like you're already there 2285 | 2286 | ## 1450. Rename 2287 | 2288 | ### 1450.1 2289 | 2290 | Still the same items. Rename the `website` folder to `website-boilerplate`. 2291 | 2292 | #### HINTS 2293 | 2294 | - Use the "move" command 2295 | - You previously used: `mv menlo.font menlo.otf` to rename a file 2296 | - Here's an example: `mv ` 2297 | - Enter `mv website website-boilerplate` in the terminal 2298 | - Make sure you are in the `project` folder first 2299 | - Enter `cd /workspace/project` to get to the `project` folder if you aren't there 2300 | - If you used the reset button, you may need to enter the above command to get to the correct folder even if it looks like you're already there 2301 | 2302 | ## 1460. List 2303 | 2304 | ### 1460.1 2305 | 2306 | List the contents of this folder to see the new name. 2307 | 2308 | #### HINTS 2309 | 2310 | - Use the "list" command 2311 | - Enter `ls` in the terminal 2312 | - Make sure you are in the `project` folder first 2313 | - Enter `cd /workspace/project` to get to the `project` folder if you aren't there 2314 | - If you used the reset button, you may need to enter the above command to get to the correct folder even if it looks like you're already there 2315 | 2316 | ## 1470. Copy Help 2317 | 2318 | ### 1470.1 2319 | 2320 | Thanks for making this. You need to make a copy of it. Take a look at the "help" menu of the "copy" command. 2321 | 2322 | #### HINTS 2323 | 2324 | - The "copy" command is `cp` 2325 | - The "help" flag is `--help` 2326 | - Enter `cp --help` in the terminal 2327 | - Make sure you are in the `project` folder first 2328 | - Enter `cd /workspace/project` to get to the `project` folder if you aren't there 2329 | - If you used the reset button, you may need to enter the above command to get to the correct folder even if it looks like you're already there 2330 | 2331 | ## 1475. Copy 2332 | 2333 | ### 1475.1 2334 | 2335 | Scroll up to find that "recursive" flag. You need to use it again to copy the whole folder. Copy the whole boilerplate into a folder named `toms-website`. 2336 | 2337 | #### HINTS 2338 | 2339 | - The "copy" command is `cp` 2340 | - The "recursive" flag is `-r` 2341 | - Here's an example: `cp -r ` 2342 | - Enter `cp -r website-boilerplate toms-website` in the terminal 2343 | - Make sure you are in the `project` folder first 2344 | - Enter `cd /workspace/project` to get to the `project` folder if you aren't there 2345 | - If you used the reset button, you may need to enter the above command to get to the correct folder even if it looks like you're already there 2346 | 2347 | ## 1480. List 2348 | 2349 | ### 1480.1 2350 | 2351 | List the contents of the `project` folder to see the new copy. 2352 | 2353 | #### HINTS 2354 | 2355 | - Use the "list" command 2356 | - Enter `ls` in the terminal 2357 | - Make sure you are in the `project` folder first 2358 | - Enter `cd /workspace/project` to get to the `project` folder if you aren't there 2359 | - If you used the reset button, you may need to enter the above command to get to the correct folder even if it looks like you're already there 2360 | 2361 | ## 1490. Find 2362 | 2363 | ### 1490.1 2364 | 2365 | Thanks. Use `find` to view the tree of `toms-website`. 2366 | 2367 | #### HINTS 2368 | 2369 | - Use the "find" command 2370 | - Add the folder name to the command 2371 | - Here's an example: `find ` 2372 | - It's the `toms-website` folder 2373 | - Enter `find toms-website` in the terminal 2374 | - Make sure you are in the `project` folder first 2375 | - Enter `cd /workspace/project` to get to the `project` folder if you aren't there 2376 | - If you used the reset button, you may need to enter the above command to get to the correct folder even if it looks like you're already there 2377 | 2378 | ## 1500. Find 2379 | 2380 | ### 1500.1 2381 | 2382 | Use `find` to view the tree of the boilerplate folder to make sure it matches. 2383 | 2384 | #### HINTS 2385 | 2386 | - Use the "find" command 2387 | - Add the folder name to the command 2388 | - It's the `website-boilerplate` folder 2389 | - Enter `find website-boilerplate` in the terminal 2390 | - Make sure you are in the `project` folder first 2391 | - Enter `cd /workspace/project` to get to the `project` folder if you aren't there 2392 | - If you used the reset button, you may need to enter the above command to get to the correct folder even if it looks like you're already there 2393 | 2394 | ## 1510. Clear 2395 | 2396 | ### 1510.1 2397 | 2398 | Awesome! You are finished for now. Clear the terminal one last time. 2399 | 2400 | #### HINTS 2401 | 2402 | - Use the "clear" command 2403 | - Enter `clear` into the terminal 2404 | 2405 | ## 1520. Echo 2406 | 2407 | ### 1520.1 2408 | 2409 | Print "goodbye terminal" to the terminal. 2410 | 2411 | #### HINTS 2412 | 2413 | - Use the "echo" command 2414 | - Here's an example: `echo ` 2415 | - Enter `echo goodbye terminal` into the terminal 2416 | 2417 | ## 1530. Exit 2418 | 2419 | ### 1530.1 2420 | 2421 | Use the "exit" command to exit the terminal. 2422 | 2423 | #### HINTS 2424 | 2425 | - Enter `exit` into the terminal 2426 | - Have a nice day 2427 | -------------------------------------------------------------------------------- /coderoad.yaml: -------------------------------------------------------------------------------- 1 | id: 'freeCodeCamp/learn-bash-by-building-a-boilerplate:v1.0.0' 2 | version: '2.0.0' 3 | config: 4 | setup: 5 | commands: 6 | - ./freeCodeCamp/setup.sh 7 | - cd freeCodeCamp && npm install 8 | testRunner: 9 | command: npm run programmatic-test 10 | args: 11 | tap: --reporter=mocha-tap-reporter 12 | directory: freeCodeCamp 13 | repo: 14 | uri: https://github.com/freeCodeCamp/learn-bash-by-building-a-boilerplate 15 | branch: v2.0.0 16 | continue: 17 | commands: 18 | - './freeCodeCamp/setup.sh' 19 | - './freeCodeCamp/reset.sh' 20 | reset: 21 | commands: 22 | - './freeCodeCamp/setup.sh' 23 | - './freeCodeCamp/reset.sh' 24 | dependencies: 25 | - name: node 26 | version: '>=10' 27 | webhook: 28 | url: 'https://api.freecodecamp.org/coderoad-challenge-completed' 29 | events: 30 | init: false 31 | reset: false 32 | step_complete: false 33 | level_complete: false 34 | tutorial_complete: true 35 | levels: 36 | - id: '5' 37 | steps: 38 | - id: '5.1' 39 | setup: 40 | watchers: 41 | - ../.bash_history 42 | - id: '10' 43 | steps: 44 | - id: '10.1' 45 | setup: 46 | watchers: 47 | - ../.bash_history 48 | - id: '20' 49 | steps: 50 | - id: '20.1' 51 | setup: 52 | watchers: 53 | - ../.bash_history 54 | - id: '30' 55 | steps: 56 | - id: '30.1' 57 | setup: 58 | watchers: 59 | - ../.bash_history 60 | - id: '40' 61 | steps: 62 | - id: '40.1' 63 | setup: 64 | watchers: 65 | - ../.bash_history 66 | - id: '50' 67 | steps: 68 | - id: '50.1' 69 | setup: 70 | watchers: 71 | - ../.bash_history 72 | - id: '60' 73 | steps: 74 | - id: '60.1' 75 | setup: 76 | watchers: 77 | - ../.bash_history 78 | - id: '70' 79 | steps: 80 | - id: '70.1' 81 | setup: 82 | watchers: 83 | - ../.bash_history 84 | - id: '80' 85 | steps: 86 | - id: '80.1' 87 | setup: 88 | watchers: 89 | - ../.bash_history 90 | - id: '90' 91 | steps: 92 | - id: '90.1' 93 | setup: 94 | watchers: 95 | - ../.bash_history 96 | - id: '100' 97 | steps: 98 | - id: '100.1' 99 | setup: 100 | watchers: 101 | - ../.bash_history 102 | - id: '110' 103 | steps: 104 | - id: '110.1' 105 | setup: 106 | watchers: 107 | - ../.bash_history 108 | - id: '120' 109 | steps: 110 | - id: '120.1' 111 | setup: 112 | watchers: 113 | - ../.bash_history 114 | - id: '130' 115 | steps: 116 | - id: '130.1' 117 | setup: 118 | watchers: 119 | - ../.bash_history 120 | - id: '140' 121 | steps: 122 | - id: '140.1' 123 | setup: 124 | watchers: 125 | - ../.bash_history 126 | - id: '150' 127 | steps: 128 | - id: '150.1' 129 | setup: 130 | watchers: 131 | - ../.bash_history 132 | - id: '160' 133 | steps: 134 | - id: '160.1' 135 | setup: 136 | watchers: 137 | - ../.bash_history 138 | - id: '170' 139 | steps: 140 | - id: '170.1' 141 | setup: 142 | watchers: 143 | - ../.bash_history 144 | - id: '180' 145 | steps: 146 | - id: '180.1' 147 | setup: 148 | watchers: 149 | - ../.bash_history 150 | - id: '181' 151 | steps: 152 | - id: '181.1' 153 | setup: 154 | watchers: 155 | - ../.bash_history 156 | - id: '182' 157 | steps: 158 | - id: '182.1' 159 | setup: 160 | watchers: 161 | - ../.bash_history 162 | - id: '183' 163 | steps: 164 | - id: '183.1' 165 | setup: 166 | watchers: 167 | - ../.bash_history 168 | - id: '184' 169 | steps: 170 | - id: '184.1' 171 | setup: 172 | watchers: 173 | - ../.bash_history 174 | - id: '185' 175 | steps: 176 | - id: '185.1' 177 | setup: 178 | watchers: 179 | - ../.bash_history 180 | - id: '190' 181 | steps: 182 | - id: '190.1' 183 | setup: 184 | watchers: 185 | - ../.bash_history 186 | - id: '200' 187 | steps: 188 | - id: '200.1' 189 | setup: 190 | watchers: 191 | - ../.bash_history 192 | - id: '210' 193 | steps: 194 | - id: '210.1' 195 | setup: 196 | watchers: 197 | - ../.bash_history 198 | - id: '220' 199 | steps: 200 | - id: '220.1' 201 | setup: 202 | watchers: 203 | - ../.bash_history 204 | - id: '230' 205 | steps: 206 | - id: '230.1' 207 | setup: 208 | watchers: 209 | - ../.bash_history 210 | - id: '240' 211 | steps: 212 | - id: '240.1' 213 | setup: 214 | watchers: 215 | - ../.bash_history 216 | - id: '250' 217 | steps: 218 | - id: '250.1' 219 | setup: 220 | watchers: 221 | - ../.bash_history 222 | - id: '260' 223 | steps: 224 | - id: '260.1' 225 | setup: 226 | watchers: 227 | - ../.bash_history 228 | - id: '270' 229 | steps: 230 | - id: '270.1' 231 | setup: 232 | watchers: 233 | - ../.bash_history 234 | - id: '280' 235 | steps: 236 | - id: '280.1' 237 | setup: 238 | watchers: 239 | - ../.bash_history 240 | - id: '285' 241 | steps: 242 | - id: '285.1' 243 | setup: 244 | watchers: 245 | - ../.bash_history 246 | - id: '290' 247 | steps: 248 | - id: '290.1' 249 | setup: 250 | watchers: 251 | - ../.bash_history 252 | - id: '300' 253 | steps: 254 | - id: '300.1' 255 | setup: 256 | watchers: 257 | - ../.bash_history 258 | - id: '310' 259 | steps: 260 | - id: '310.1' 261 | setup: 262 | watchers: 263 | - ../.bash_history 264 | - id: '320' 265 | steps: 266 | - id: '320.1' 267 | setup: 268 | watchers: 269 | - ../.bash_history 270 | - id: '330' 271 | steps: 272 | - id: '330.1' 273 | setup: 274 | watchers: 275 | - ../.bash_history 276 | - id: '340' 277 | steps: 278 | - id: '340.1' 279 | setup: 280 | watchers: 281 | - ../.bash_history 282 | - id: '350' 283 | steps: 284 | - id: '350.1' 285 | setup: 286 | watchers: 287 | - ../.bash_history 288 | - id: '360' 289 | steps: 290 | - id: '360.1' 291 | setup: 292 | watchers: 293 | - ../.bash_history 294 | - id: '370' 295 | steps: 296 | - id: '370.1' 297 | setup: 298 | watchers: 299 | - ../.bash_history 300 | - id: '380' 301 | steps: 302 | - id: '380.1' 303 | setup: 304 | watchers: 305 | - ../.bash_history 306 | - id: '390' 307 | steps: 308 | - id: '390.1' 309 | setup: 310 | watchers: 311 | - ../.bash_history 312 | - id: '400' 313 | steps: 314 | - id: '400.1' 315 | setup: 316 | watchers: 317 | - ../.bash_history 318 | - id: '410' 319 | steps: 320 | - id: '410.1' 321 | setup: 322 | watchers: 323 | - ../.bash_history 324 | - id: '420' 325 | steps: 326 | - id: '420.1' 327 | setup: 328 | watchers: 329 | - ../.bash_history 330 | - id: '430' 331 | steps: 332 | - id: '430.1' 333 | setup: 334 | watchers: 335 | - ../.bash_history 336 | - id: '440' 337 | steps: 338 | - id: '440.1' 339 | setup: 340 | watchers: 341 | - ../.bash_history 342 | - id: '450' 343 | steps: 344 | - id: '450.1' 345 | setup: 346 | watchers: 347 | - ../.bash_history 348 | - id: '460' 349 | steps: 350 | - id: '460.1' 351 | setup: 352 | watchers: 353 | - ../.bash_history 354 | - id: '470' 355 | steps: 356 | - id: '470.1' 357 | setup: 358 | watchers: 359 | - ../.bash_history 360 | - id: '480' 361 | steps: 362 | - id: '480.1' 363 | setup: 364 | watchers: 365 | - ../.bash_history 366 | - id: '490' 367 | steps: 368 | - id: '490.1' 369 | setup: 370 | watchers: 371 | - ../.bash_history 372 | - id: '500' 373 | steps: 374 | - id: '500.1' 375 | setup: 376 | watchers: 377 | - ../.bash_history 378 | - id: '510' 379 | steps: 380 | - id: '510.1' 381 | setup: 382 | watchers: 383 | - ../.bash_history 384 | - id: '520' 385 | steps: 386 | - id: '520.1' 387 | setup: 388 | watchers: 389 | - ../.bash_history 390 | - id: '530' 391 | steps: 392 | - id: '530.1' 393 | setup: 394 | watchers: 395 | - ../.bash_history 396 | - id: '540' 397 | steps: 398 | - id: '540.1' 399 | setup: 400 | watchers: 401 | - ../.bash_history 402 | - id: '550' 403 | steps: 404 | - id: '550.1' 405 | setup: 406 | watchers: 407 | - ../.bash_history 408 | - id: '560' 409 | steps: 410 | - id: '560.1' 411 | setup: 412 | watchers: 413 | - ../.bash_history 414 | - id: '570' 415 | steps: 416 | - id: '570.1' 417 | setup: 418 | watchers: 419 | - ../.bash_history 420 | - id: '580' 421 | steps: 422 | - id: '580.1' 423 | setup: 424 | watchers: 425 | - ../.bash_history 426 | - id: '585' 427 | steps: 428 | - id: '585.1' 429 | setup: 430 | watchers: 431 | - ../.bash_history 432 | - id: '590' 433 | steps: 434 | - id: '590.1' 435 | setup: 436 | watchers: 437 | - ../.bash_history 438 | - id: '600' 439 | steps: 440 | - id: '600.1' 441 | setup: 442 | watchers: 443 | - ../.bash_history 444 | - id: '610' 445 | steps: 446 | - id: '610.1' 447 | setup: 448 | watchers: 449 | - ../.bash_history 450 | - id: '620' 451 | steps: 452 | - id: '620.1' 453 | setup: 454 | watchers: 455 | - ../.bash_history 456 | - id: '630' 457 | steps: 458 | - id: '630.1' 459 | setup: 460 | watchers: 461 | - ../.bash_history 462 | - id: '640' 463 | steps: 464 | - id: '640.1' 465 | setup: 466 | watchers: 467 | - ../.bash_history 468 | - id: '650' 469 | steps: 470 | - id: '650.1' 471 | setup: 472 | watchers: 473 | - ../.bash_history 474 | - id: '660' 475 | steps: 476 | - id: '660.1' 477 | setup: 478 | watchers: 479 | - ../.bash_history 480 | - id: '670' 481 | steps: 482 | - id: '670.1' 483 | setup: 484 | watchers: 485 | - ../.bash_history 486 | - id: '680' 487 | steps: 488 | - id: '680.1' 489 | setup: 490 | watchers: 491 | - ../.bash_history 492 | - id: '690' 493 | steps: 494 | - id: '690.1' 495 | setup: 496 | watchers: 497 | - ../.bash_history 498 | - id: '700' 499 | steps: 500 | - id: '700.1' 501 | setup: 502 | watchers: 503 | - ../.bash_history 504 | - id: '710' 505 | steps: 506 | - id: '710.1' 507 | setup: 508 | watchers: 509 | - ../.bash_history 510 | - id: '720' 511 | steps: 512 | - id: '720.1' 513 | setup: 514 | watchers: 515 | - ../.bash_history 516 | - id: '730' 517 | steps: 518 | - id: '730.1' 519 | setup: 520 | watchers: 521 | - ../.bash_history 522 | - id: '740' 523 | steps: 524 | - id: '740.1' 525 | setup: 526 | watchers: 527 | - ../.bash_history 528 | - id: '750' 529 | steps: 530 | - id: '750.1' 531 | setup: 532 | watchers: 533 | - ../.bash_history 534 | - id: '755' 535 | steps: 536 | - id: '755.1' 537 | setup: 538 | watchers: 539 | - ../.bash_history 540 | - id: '760' 541 | steps: 542 | - id: '760.1' 543 | setup: 544 | watchers: 545 | - ../.bash_history 546 | - id: '770' 547 | steps: 548 | - id: '770.1' 549 | setup: 550 | watchers: 551 | - ../.bash_history 552 | - id: '780' 553 | steps: 554 | - id: '780.1' 555 | setup: 556 | watchers: 557 | - ../.bash_history 558 | - id: '790' 559 | steps: 560 | - id: '790.1' 561 | setup: 562 | watchers: 563 | - ../.bash_history 564 | - id: '800' 565 | steps: 566 | - id: '800.1' 567 | setup: 568 | watchers: 569 | - ../.bash_history 570 | - id: '850' 571 | steps: 572 | - id: '850.1' 573 | setup: 574 | watchers: 575 | - ../.bash_history 576 | - id: '860' 577 | steps: 578 | - id: '860.1' 579 | setup: 580 | watchers: 581 | - ../.bash_history 582 | - id: '870' 583 | steps: 584 | - id: '870.1' 585 | setup: 586 | watchers: 587 | - ../.bash_history 588 | - id: '880' 589 | steps: 590 | - id: '880.1' 591 | setup: 592 | watchers: 593 | - ../.bash_history 594 | - id: '890' 595 | steps: 596 | - id: '890.1' 597 | setup: 598 | watchers: 599 | - ../.bash_history 600 | - id: '900' 601 | steps: 602 | - id: '900.1' 603 | setup: 604 | watchers: 605 | - ../.bash_history 606 | - id: '910' 607 | steps: 608 | - id: '910.1' 609 | setup: 610 | watchers: 611 | - ../.bash_history 612 | - id: '920' 613 | steps: 614 | - id: '920.1' 615 | setup: 616 | watchers: 617 | - ../.bash_history 618 | - id: '930' 619 | steps: 620 | - id: '930.1' 621 | setup: 622 | watchers: 623 | - ../.bash_history 624 | - id: '940' 625 | steps: 626 | - id: '940.1' 627 | setup: 628 | watchers: 629 | - ../.bash_history 630 | - id: '950' 631 | steps: 632 | - id: '950.1' 633 | setup: 634 | watchers: 635 | - ../.bash_history 636 | - id: '960' 637 | steps: 638 | - id: '960.1' 639 | setup: 640 | watchers: 641 | - ../.bash_history 642 | - id: '970' 643 | steps: 644 | - id: '970.1' 645 | setup: 646 | watchers: 647 | - ../.bash_history 648 | - id: '980' 649 | steps: 650 | - id: '980.1' 651 | setup: 652 | watchers: 653 | - ../.bash_history 654 | - id: '990' 655 | steps: 656 | - id: '990.1' 657 | setup: 658 | watchers: 659 | - ../.bash_history 660 | - id: '1000' 661 | steps: 662 | - id: '1000.1' 663 | setup: 664 | watchers: 665 | - ../.bash_history 666 | - id: '1010' 667 | steps: 668 | - id: '1010.1' 669 | setup: 670 | watchers: 671 | - ../.bash_history 672 | - id: '1020' 673 | steps: 674 | - id: '1020.1' 675 | setup: 676 | watchers: 677 | - ../.bash_history 678 | - id: '1030' 679 | steps: 680 | - id: '1030.1' 681 | setup: 682 | watchers: 683 | - ../.bash_history 684 | - id: '1040' 685 | steps: 686 | - id: '1040.1' 687 | setup: 688 | watchers: 689 | - ../.bash_history 690 | - id: '1050' 691 | steps: 692 | - id: '1050.1' 693 | setup: 694 | watchers: 695 | - ../.bash_history 696 | - id: '1055' 697 | steps: 698 | - id: '1055.1' 699 | setup: 700 | watchers: 701 | - ../.bash_history 702 | - id: '1060' 703 | steps: 704 | - id: '1060.1' 705 | setup: 706 | watchers: 707 | - ../.bash_history 708 | - id: '1065' 709 | steps: 710 | - id: '1065.1' 711 | setup: 712 | watchers: 713 | - ../.bash_history 714 | - id: '1070' 715 | steps: 716 | - id: '1070.1' 717 | setup: 718 | watchers: 719 | - ../.bash_history 720 | - id: '1080' 721 | steps: 722 | - id: '1080.1' 723 | setup: 724 | watchers: 725 | - ../.bash_history 726 | - id: '1090' 727 | steps: 728 | - id: '1090.1' 729 | setup: 730 | watchers: 731 | - ../.bash_history 732 | - id: '1100' 733 | steps: 734 | - id: '1100.1' 735 | setup: 736 | watchers: 737 | - ../.bash_history 738 | - id: '1110' 739 | steps: 740 | - id: '1110.1' 741 | setup: 742 | watchers: 743 | - ../.bash_history 744 | - id: '1120' 745 | steps: 746 | - id: '1120.1' 747 | setup: 748 | watchers: 749 | - ../.bash_history 750 | - id: '1130' 751 | steps: 752 | - id: '1130.1' 753 | setup: 754 | watchers: 755 | - ../.bash_history 756 | - id: '1135' 757 | steps: 758 | - id: '1135.1' 759 | setup: 760 | watchers: 761 | - ../.bash_history 762 | - id: '1150' 763 | steps: 764 | - id: '1150.1' 765 | setup: 766 | watchers: 767 | - ../.bash_history 768 | - id: '1170' 769 | steps: 770 | - id: '1170.1' 771 | setup: 772 | watchers: 773 | - ../.bash_history 774 | - id: '1190' 775 | steps: 776 | - id: '1190.1' 777 | setup: 778 | watchers: 779 | - ../.bash_history 780 | - id: '1195' 781 | steps: 782 | - id: '1195.1' 783 | setup: 784 | watchers: 785 | - ../.bash_history 786 | - id: '1200' 787 | steps: 788 | - id: '1200.1' 789 | setup: 790 | watchers: 791 | - ../.bash_history 792 | - id: '1210' 793 | steps: 794 | - id: '1210.1' 795 | setup: 796 | watchers: 797 | - ../.bash_history 798 | - id: '1215' 799 | steps: 800 | - id: '1215.1' 801 | setup: 802 | watchers: 803 | - ../.bash_history 804 | - id: '1220' 805 | steps: 806 | - id: '1220.1' 807 | setup: 808 | watchers: 809 | - ../.bash_history 810 | - id: '1230' 811 | steps: 812 | - id: '1230.1' 813 | setup: 814 | watchers: 815 | - ../.bash_history 816 | - id: '1240' 817 | steps: 818 | - id: '1240.1' 819 | setup: 820 | watchers: 821 | - ../.bash_history 822 | - id: '1250' 823 | steps: 824 | - id: '1250.1' 825 | setup: 826 | watchers: 827 | - ../.bash_history 828 | - id: '1260' 829 | steps: 830 | - id: '1260.1' 831 | setup: 832 | watchers: 833 | - ../.bash_history 834 | - id: '1270' 835 | steps: 836 | - id: '1270.1' 837 | setup: 838 | watchers: 839 | - ../.bash_history 840 | - id: '1275' 841 | steps: 842 | - id: '1275.1' 843 | setup: 844 | watchers: 845 | - ../.bash_history 846 | - id: '1280' 847 | steps: 848 | - id: '1280.1' 849 | setup: 850 | watchers: 851 | - ../.bash_history 852 | - id: '1290' 853 | steps: 854 | - id: '1290.1' 855 | setup: 856 | watchers: 857 | - ../.bash_history 858 | - id: '1300' 859 | steps: 860 | - id: '1300.1' 861 | setup: 862 | watchers: 863 | - ../.bash_history 864 | - id: '1310' 865 | steps: 866 | - id: '1310.1' 867 | setup: 868 | watchers: 869 | - ../.bash_history 870 | - id: '1315' 871 | steps: 872 | - id: '1315.1' 873 | setup: 874 | watchers: 875 | - ../.bash_history 876 | - id: '1320' 877 | steps: 878 | - id: '1320.1' 879 | setup: 880 | watchers: 881 | - ../.bash_history 882 | - id: '1330' 883 | steps: 884 | - id: '1330.1' 885 | setup: 886 | watchers: 887 | - ../.bash_history 888 | - id: '1340' 889 | steps: 890 | - id: '1340.1' 891 | setup: 892 | watchers: 893 | - ../.bash_history 894 | - id: '1350' 895 | steps: 896 | - id: '1350.1' 897 | setup: 898 | watchers: 899 | - ../.bash_history 900 | - id: '1360' 901 | steps: 902 | - id: '1360.1' 903 | setup: 904 | watchers: 905 | - ../.bash_history 906 | - id: '1370' 907 | steps: 908 | - id: '1370.1' 909 | setup: 910 | watchers: 911 | - ../.bash_history 912 | - id: '1380' 913 | steps: 914 | - id: '1380.1' 915 | setup: 916 | watchers: 917 | - ../.bash_history 918 | - id: '1390' 919 | steps: 920 | - id: '1390.1' 921 | setup: 922 | watchers: 923 | - ../.bash_history 924 | - id: '1400' 925 | steps: 926 | - id: '1400.1' 927 | setup: 928 | watchers: 929 | - ../.bash_history 930 | - id: '1405' 931 | steps: 932 | - id: '1405.1' 933 | setup: 934 | watchers: 935 | - ../.bash_history 936 | - id: '1410' 937 | steps: 938 | - id: '1410.1' 939 | setup: 940 | watchers: 941 | - ../.bash_history 942 | - id: '1415' 943 | steps: 944 | - id: '1415.1' 945 | setup: 946 | watchers: 947 | - ../.bash_history 948 | - id: '1420' 949 | steps: 950 | - id: '1420.1' 951 | setup: 952 | watchers: 953 | - ../.bash_history 954 | - id: '1430' 955 | steps: 956 | - id: '1430.1' 957 | setup: 958 | watchers: 959 | - ../.bash_history 960 | - id: '1440' 961 | steps: 962 | - id: '1440.1' 963 | setup: 964 | watchers: 965 | - ../.bash_history 966 | - id: '1445' 967 | steps: 968 | - id: '1445.1' 969 | setup: 970 | watchers: 971 | - ../.bash_history 972 | - id: '1450' 973 | steps: 974 | - id: '1450.1' 975 | setup: 976 | watchers: 977 | - ../.bash_history 978 | - id: '1460' 979 | steps: 980 | - id: '1460.1' 981 | setup: 982 | watchers: 983 | - ../.bash_history 984 | - id: '1470' 985 | steps: 986 | - id: '1470.1' 987 | setup: 988 | watchers: 989 | - ../.bash_history 990 | - id: '1475' 991 | steps: 992 | - id: '1475.1' 993 | setup: 994 | watchers: 995 | - ../.bash_history 996 | - id: '1480' 997 | steps: 998 | - id: '1480.1' 999 | setup: 1000 | watchers: 1001 | - ../.bash_history 1002 | - id: '1490' 1003 | steps: 1004 | - id: '1490.1' 1005 | setup: 1006 | watchers: 1007 | - ../.bash_history 1008 | - id: '1500' 1009 | steps: 1010 | - id: '1500.1' 1011 | setup: 1012 | watchers: 1013 | - ../.bash_history 1014 | - id: '1510' 1015 | steps: 1016 | - id: '1510.1' 1017 | setup: 1018 | watchers: 1019 | - ../.bash_history 1020 | - id: '1520' 1021 | steps: 1022 | - id: '1520.1' 1023 | setup: 1024 | watchers: 1025 | - ../.bash_history 1026 | - id: '1530' 1027 | steps: 1028 | - id: '1530.1' 1029 | setup: 1030 | watchers: 1031 | - ../.bash_history 1032 | -------------------------------------------------------------------------------- /freeCodeCamp/.bashrc: -------------------------------------------------------------------------------- 1 | # ~/.bashrc: executed by bash(1) for non-login shells. 2 | # see /usr/share/doc/bash/examples/startup-files (in the package bash-doc) 3 | # for examples 4 | 5 | # If not running interactively, don't do anything 6 | case $- in 7 | *i*) ;; 8 | *) return;; 9 | esac 10 | 11 | # don't put duplicate lines or lines starting with space in the history. 12 | # See bash(1) for more options 13 | # I commented this out 14 | #HISTCONTROL=ignoreboth 15 | 16 | # append to the history file, don't overwrite it 17 | shopt -s histappend 18 | 19 | # for setting history length see HISTSIZE and HISTFILESIZE in bash(1) 20 | HISTSIZE=1000 21 | HISTFILESIZE=2000 22 | 23 | # check the window size after each command and, if necessary, 24 | # update the values of LINES and COLUMNS. 25 | shopt -s checkwinsize 26 | 27 | # If set, the pattern "**" used in a pathname expansion context will 28 | # match all files and zero or more directories and subdirectories. 29 | #shopt -s globstar 30 | 31 | # make less more friendly for non-text input files, see lesspipe(1) 32 | # I commented this out 33 | #[ -x /usr/bin/lesspipe ] && eval "$(SHELL=/bin/sh lesspipe)" 34 | 35 | # set variable identifying the chroot you work in (used in the prompt below) 36 | if [ -z "${debian_chroot:-}" ] && [ -r /etc/debian_chroot ]; then 37 | debian_chroot=$(cat /etc/debian_chroot) 38 | fi 39 | 40 | # set a fancy prompt (non-color, unless we know we "want" color) 41 | case "$TERM" in 42 | xterm-color|*-256color) color_prompt=yes;; 43 | esac 44 | 45 | # uncomment for a colored prompt, if the terminal has the capability; turned 46 | # off by default to not distract the user: the focus in a terminal window 47 | # should be on the output of commands, not on the prompt 48 | #force_color_prompt=yes 49 | 50 | if [ -n "$force_color_prompt" ]; then 51 | if [ -x /usr/bin/tput ] && tput setaf 1 >&/dev/null; then 52 | # We have color support; assume it's compliant with Ecma-48 53 | # (ISO/IEC-6429). (Lack of such support is extremely rare, and such 54 | # a case would tend to support setf rather than setaf.) 55 | color_prompt=yes 56 | else 57 | color_prompt= 58 | fi 59 | fi 60 | 61 | if [ "$color_prompt" = yes ]; then 62 | PS1='${debian_chroot:+($debian_chroot)}\[\033[01;32m\]\u@\h\[\033[00m\]:\[\033[01;34m\]\w\[\033[00m\]\$ ' 63 | else 64 | PS1='${debian_chroot:+($debian_chroot)}\u@\h:\w\$ ' 65 | fi 66 | unset color_prompt force_color_prompt 67 | 68 | # If this is an xterm set the title to user@host:dir 69 | case "$TERM" in 70 | xterm*|rxvt*) 71 | PS1="\[\e]0;${debian_chroot:+($debian_chroot)}\u@\h: \w\a\]$PS1" 72 | ;; 73 | *) 74 | ;; 75 | esac 76 | 77 | # enable color support of ls and also add handy aliases 78 | if [ -x /usr/bin/dircolors ]; then 79 | test -r ~/.dircolors && eval "$(dircolors -b ~/.dircolors)" || eval "$(dircolors -b)" 80 | alias ls='ls --color=auto' 81 | #alias dir='dir --color=auto' 82 | #alias vdir='vdir --color=auto' 83 | 84 | # I commented these out 85 | # alias grep='grep --color=auto' 86 | # alias fgrep='fgrep --color=auto' 87 | # alias egrep='egrep --color=auto' 88 | fi 89 | 90 | # colored GCC warnings and errors 91 | #export GCC_COLORS='error=01;31:warning=01;35:note=01;36:caret=01;32:locus=01:quote=01' 92 | 93 | # some more ls aliases - # I commented these out 94 | # alias ll='ls -alF' 95 | # alias la='ls -A' 96 | # alias l='ls -CF' 97 | 98 | # Add an "alert" alias for long running commands. Use like so: 99 | # sleep 10; alert 100 | # I commented this out 101 | #alias alert='notify-send --urgency=low -i "$([ $? = 0 ] && echo terminal || echo error)" "$(history|tail -n1|sed -e '\''s/^\s*[0-9]\+\s*//;s/[;&|]\s*alert$//'\'')"' 102 | 103 | # Alias definitions. 104 | # You may want to put all your additions into a separate file like 105 | # ~/.bash_aliases, instead of adding them here directly. 106 | # See /usr/share/doc/bash-doc/examples in the bash-doc package. 107 | 108 | if [ -f ~/.bash_aliases ]; then 109 | . ~/.bash_aliases 110 | fi 111 | 112 | # enable programmable completion features (you don't need to enable 113 | # this, if it's already enabled in /etc/bash.bashrc and /etc/profile 114 | # sources /etc/bash.bashrc). 115 | if ! shopt -oq posix; then 116 | if [ -f /usr/share/bash-completion/bash_completion ]; then 117 | . /usr/share/bash-completion/bash_completion 118 | elif [ -f /etc/bash_completion ]; then 119 | . /etc/bash_completion 120 | fi 121 | fi 122 | 123 | # I commented this out 124 | #for i in $(ls -A $HOME/.bashrc.d/); do source $HOME/.bashrc.d/$i; done 125 | 126 | # Add RVM to PATH for scripting. Make sure this is the last PATH variable change. 127 | export PATH="$PATH:$HOME/.rvm/bin" 128 | 129 | # stuff I added 130 | PS1='camper: \[\033[01;34m\]/${PWD##*/}\[\033[00m\]\$ ' 131 | HISTFILE=/workspace/.bash_history 132 | PROMPT_COMMAND='echo $PWD >> /workspace/project/freeCodeCamp/test/.cwd; history -a' 133 | trap 'echo $BASH_COMMAND >> /workspace/project/freeCodeCamp/test/.next_command' DEBUG -------------------------------------------------------------------------------- /freeCodeCamp/test/.cwd: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Navonnik/learn-bash-by-building-a-boilerplate/b47da2f1aefd5ecd3a04aaf48b0ac5b8b779948b/freeCodeCamp/test/.cwd -------------------------------------------------------------------------------- /freeCodeCamp/test/.next_command: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Navonnik/learn-bash-by-building-a-boilerplate/b47da2f1aefd5ecd3a04aaf48b0ac5b8b779948b/freeCodeCamp/test/.next_command --------------------------------------------------------------------------------