Zero to Terminal
From “I’ve never used a terminal” to serving a website and checking it in a browser
Who Is This Track For?
Section titled “Who Is This Track For?”This track is for absolute beginners. Module 0.1 needs no technical experience. Before exercises, read each module’s platform and cost notes where applicable.
Module 0.11 uses a browser to check the website. Modules 0.3–0.11 use Unix-style commands. On Windows, use a Linux shell such as WSL or a lab shell where the modules suggest one; Module 0.2 introduces WSL and also offers a PowerShell option for that module. See Microsoft’s WSL installation guide for setup.
The capstone offers two paths. The local path needs a preconfigured Docker Engine on a computer you are authorized to use. Module 0.11 explains how to check that Docker is connected to your local machine and that the server version is at least 28.0.0. The cloud path needs an authorized disposable VM, instructor-provided or created through a provider account; account steps and billing may apply. The track does not set these up for you. If neither environment is available, read the examples without starting resources.
What You’ll Learn
Section titled “What You’ll Learn”By the end of this track, you’ll be able to:
- Understand what’s happening inside your computer (and why it matters)
- Use the terminal (command line) to navigate, create, and manage files
- Edit files using a text editor right in the terminal
- Understand networking, servers, and how to connect to them remotely
- Know what “the cloud” actually means (spoiler: it’s not magic)
- Use terminal commands to serve a website and check it in a browser: locally on loopback, or on an authorized cloud VM for a public test
This track leads into the main prerequisites route — Cloud Native 101 and then Kubernetes Basics — with Linux as an optional systems fork you can pick up anytime.
Optional first-terminal preview
Section titled “Optional first-terminal preview”Before starting the ordered route, you may preview the terminal opening and prompt guide and first safe-command exercise. Use Module 0.2’s own platform guidance. Then return to Module 0.1 and complete the modules in order; the preview does not replace the track.
The Restaurant Kitchen Analogy
Section titled “The Restaurant Kitchen Analogy”Several modules use a restaurant kitchen analogy to introduce these terms:
| Computer Concept | Kitchen Equivalent |
|---|---|
| CPU | The chef (does the work) |
| RAM | Counter space (temporary workspace) |
| Disk/SSD | The pantry (long-term storage) |
| Operating System | The restaurant manager |
| Programs | Recipes |
| Server | A restaurant kitchen (handles requests) |
| Cloud | Renting a commercial kitchen instead of building your own |
The kitchen analogy is not a literal model. The terminal application displays text and accepts keyboard input; a shell reads your command line and starts commands. File permissions govern access to files. CPUs can have many cores, not just one chef. A server may be a program serving requests or the computer running it. Cloud services can be public or private, and renting a kitchen does not capture that distinction. Disk storage can outlast a power-off, but can still fail or be lost: keep backups of important data. The technical explanations, platform notes, and exercises give the details.
Modules
Section titled “Modules”| Module | Title | Time | What You’ll Learn |
|---|---|---|---|
| 0.1 | What is a Computer? | 90–120 min | CPU, RAM, disk, OS — the kitchen hardware |
| 0.2 | What is a Terminal? | 90–120 min | Opening and understanding the terminal |
| 0.3 | First Terminal Commands | 80–100 min | Navigate, create, move, and delete files |
| 0.4 | Files and Directories | 90–120 min | Paths, file types, organizing your filesystem |
| 0.5 | Editing Files | 80–100 min | Edit files with nano, write your first script |
| 0.6 | Git Basics — Track Your Work | 90–120 min | Track your work with Git — init, add, commit, log |
| 0.7 | What is Networking? | 90–120 min | IPs, ports, DNS — how computers talk to each other |
| 0.8 | Servers and SSH | 80–100 min | What servers are, how to connect remotely |
| 0.9 | Software and Packages | 80–100 min | Installing and managing software from the terminal |
| 0.10 | What is the Cloud? | 80–100 min | Cloud computing, AWS/Azure/GCP, where K8s fits |
| 0.11 | Your First Server — Putting It All Together | 90–120 min | Capstone: serve and check a small website |
These ranges are the Time to Complete values from the eleven module headers. Their arithmetic gives an aggregate range of 940–1220 minutes (about 15 hours 40 minutes–20 hours 20 minutes).
How to Use This Track
Section titled “How to Use This Track”- Follow the suggested order. Later exercises combine earlier skills, although some introductions can stand alone.
- Do the exercises. Read the explanation, try the task, and compare your result with the success criteria.
What’s Next?
Section titled “What’s Next?”On the suggested prerequisites route, continue to Cloud Native 101 and then Kubernetes Basics.
Default next step: Cloud Native 101 — containers, Docker, and the cloud-native ecosystem.
Optional fork: Linux if you want deeper systems knowledge. Linux is not required before Cloud Native 101; you can pick it up anytime.
Zero to Terminal | Module 0.11 (Capstone) | Cloud Native 101 (default — suggested route) | Kubernetes Basics | ...
Linux (optional fork — anytime)