A platform for production infrastructure education.

RunBook Academy teaches infrastructure technologies and how to operate them safely in production. The central educational philosophy is:teach people not only how infrastructure works, but how to operate it safely in production.

That means every lesson emphasises:

• production operations and day-2 care;
• troubleshooting and incident response;
• security and resilience;
• observability and performance;
• backup and disaster recovery;
• practical laboratories that build muscle memory.

What is on the platform right now

6 courses — Linux, Docker & Containers, Proxmox VE and Ansible — across 367 parts and roughly 999 hours of material: 2289 lessons, 197 labs, 149 runbooks, 79 checklists and 145 break/fix scenarios, plus a final assessment for each course.

Every course is written to the same standard and none is a stub. They differ in emphasis rather than maturity: Linux is the broadest, Ansible goes deepest on a single tool, Proxmox and Docker sit between the two. The catalogue lists the size and target versions of each.

Before you run anything

This material is published without warranty, and much of it changes production systems. Commands that reconfigure storage, networking, firewalls, cluster membership or SSH access can take a host off the network or destroy data if they are run in the wrong place or on a version they were not written for.

• Run it somewhere disposable first. A VM, a nested cluster, a scratch host — not the thing your users depend on.
• Check the version. Each course states the software versions it targets. A flag that is correct on one release can be rejected outright on another, and an unknown keyword usually stops the service rather than being ignored.
• Read the severity badge on a command block before you run it, and keep a second session open whenever you are changing something you connect through.
• No lab in any course has been executed end to end by us.Lab pages say so individually. Treat them as designs to work through, not as scripts known to run clean.

You are responsible for what you run on your own systems. If a command here does not match your platform's documentation, trust your platform.

How to read

1. Pick the course that matches your role from the catalogue.
2. Read the landing page for the prerequisites and learning outcomes.
3. Work through the curriculum in order; later parts assume earlier material.
4. Do the labs and break/fix scenarios — they are the muscle-memory builders.
5. Keep the runbooks and checklists to hand during real work — but read a runbook through once before you follow it under pressure, and verify its commands against your own version first.

Verified content

Every course declares which software versions the content targets, and when each lesson was last re-verified. The build surfaces stale content so that re-verification work can be tracked. Where a claim could not be confirmed against upstream documentation, the content says so rather than asserting it.

Platform

A multi-course fully static site built on Astro 7 with Svelte 5 islands for interactivity. There is no account system, no tracking, and no server-side component: nothing you do here leaves your browser unless you explicitly export it.

Your theme, lesson completion and quiz scores are stored inlocalStorage under the key runbook:progress:v2, namespaced per course. Each course landing page has an Exportbutton that downloads the record as JSON; an Import button accepts the same shape and merges it into the current browser. Clearing browser data erases the record — there is no server-side copy.

Open source

Course content is licensed under CC BY-SA 4.0and platform code under the MIT License — both, as those licences state, without warranty of any kind. Contributions and corrections are welcome; if you find a command here that is wrong, please report it.