Absolute Path

DevOps and cloud engineer

Keep software running, from the first commit to the live site.

A DevOps engineer builds the route that code takes from a developer's computer to the live service, and keeps that service healthy. You learn the command line, Git, pipelines, containers, cloud services, and monitoring.

  • Planned
  • 1 of 7 courses ready
  • About 21 hours in total
  • Free

Not started

Start the path

Your path, step by step

The course list is set. You can start with the courses that are ready. A step with no link is a course that is planned. Its time is an estimate.

  1. Python

    Up next

    Learn a clear, friendly language used almost everywhere.

    • Beginner
    • 10 lessons
    • 1 h 54 min

    Not started

    Why this step: You use a scripting language to automate work. Python is a common choice.

  2. Linux command line

    Coming soon

    Move around, work with files, and run programs from the terminal.

    • About 3 h

    Why this step: Most servers run Linux. You work with it from the terminal.

  3. Git and GitHub

    Coming soon

    Save your work in steps, go back when you need to, and share your code.

    • About 2 h 30 min

    Why this step: Everything that you automate starts from code in Git.

  4. CI pipelines

    Coming soon

    Run checks and tests on every code change with GitHub Actions, and read the results.

    • About 3 h

    Why this step: You build the pipeline that checks and builds the code on every change.

  5. Containers with Docker

    Coming soon

    Package an app so that it runs the same way on every computer.

    • About 4 h

    Why this step: A container runs the same way on your computer and on the server.

  6. Cloud basics

    Coming soon

    Run an app on a cloud service, and learn about servers, storage, and cost.

    • About 4 h

    Why this step: You run the app on a cloud service, and you learn what it costs.

  7. Monitoring and logs

    Coming soon

    Find out when an app has a problem, and find the cause in its logs.

    • About 2 h 30 min

    Why this step: You find out when an app has a problem, and why.