World map

 

BM

World T1: Blueprints

Clicking vs writing it down

You will learn: why teams write their servers down as a blueprint.

Checked with OpenTofu 1.13 on 1 Nov 2026

The problem

You set up Kedai Kancil’s stall by clicking 40 buttons on a website. The boss says: “Make the same one in Penang.” What goes wrong?

Watch

Tap each point on the timeline.

An architect draws first, then builds. Writing your setup down like this is infrastructure as code (IaC): Writing your servers and settings down as text files, like a blueprint. A tool then builds exactly what the files say.. Tap each step.

Try it

This file, main.tf, is a blueprint. It asks for one thing: sign.txt. Type tofu apply, then yes.

Blueprint (your .tf files)init done

  • local_file.signnot built yet

Built (the state file)

Nothing built yet.

Blueprint: 1 resources. Built: 0.

Change a file, then run tofu plan to see what it means.

Predict

Your friend runs the same main.tf on her own laptop. What does she get?

Check

Clicking or a blueprint? Sort each one.

Drag a card into a box. Or tap the card, then tap the box.

      You did it!

      You can now explain why teams draw a blueprint instead of clicking.

      Go deeper (optional)

      These lessons use OpenTofu (the tofu command). Terraform (terraform) reads the same files; lesson 8 compares them. Other tools exist too. The idea stays the same: draw, inspect, build.

      Real rep (optional), on your own computer. The local provider only writes files, so nothing costs money.

      Real mission

      2. mkdir kedai && cd kedai
      4. tofu init
      5. tofu apply
      6. cat sign.txt

      0 of 6 steps done · Your ticks are saved.