From your first prompt to debugging a broken server. Each stage builds on the one before it.
Everything this course covers, in the order you'll learn it. Open a stage to see why it matters and jump to its lesson.
Find your way around any server without a GUI. Everything else depends on this.
Lesson 1: The shell and the filesystem →Config lives in text files. You need to edit them over SSH, where there is no VS Code.
Lesson 2: Editing files: nano, vim, and changing a server safely →Know how the shell finds commands, where output goes, and when you are root.
Lesson 3: Shell basics: PATH, variables, streams and sudo →Most "it works on my machine" bugs are really permission or path problems.
Lesson 4: Working with files: permissions, archives and links →Logs are text. Small tools joined with pipes answer most incident questions in seconds.
Lesson 5: Text processing: get answers out of logs →The five-minute health check you run the moment you log into a slow server.
Lesson 6: Server review: a five-minute health check →Find what is eating the CPU, stop it cleanly, and keep jobs running after you log out.
Lesson 7: Processes: see them, control them, stop them →Every service should run as its own user. This is the first layer of security.
Lesson 8: Users and groups: who can do what →How real apps run on servers: start on boot, restart on crash, logs in one place.
Lesson 9: Services with systemd: run, restart, read the logs →Install, pin and upgrade software the same way on every server.
Lesson 10: Packages: install, update and trust software →"Disk full" is one of the most common outages. Learn to find space and add more.
Lesson 11: Disks and filesystems: add, mount, grow and repair →When a server will not come back after a reboot, this is where you look.
Lesson 12: How Linux boots, and what to do when it does not →Half of DevOps debugging is "can A talk to B?". These are the building blocks.
Lesson 13: Networking: addresses, DNS, routes and SSH →Turn the commands you repeat into scripts that run the same way every time.
Lesson 14: Shell scripting: automate it once, run it forever →A calm, repeatable way to find out why the network or a service is broken.
Lesson 15: Troubleshooting the network: from "it is down" to the cause →Containers are just Linux features. This stage is the bridge to the Docker course.
Lesson 16: Containers are Linux: namespaces, cgroups and Docker →Stage order follows the community roadmap at roadmap.sh/linux, trimmed to what DevOps work needs.