Rullst AcademyRullst Academy/Lesson
From application to release with Rullst · Lesson 01 / 12

A release someone else can reproduce

Your mission board works. Now it needs to work in another session, using instructions you can explain. Your first opponent is “it works on my machine”.

Learning paths25 min

Let's discover together

  1. 1

    Preparation: can you run the Applications with Rullst I board and explain where it saves a mission? If not, use the linked track. You do not need to complete every previous track.

  2. 2

    Download this lesson’s materials into a new folder. Open the folder containing Cargo.toml. Read README.md: Rust is the language; Rullst 12.1.1 supplies the web framework and data integration. This ZIP contains server source, not just a PWA shortcut.

  3. 3

    Run cargo test --locked, then cargo run --locked -- serve. The first build may take time and download dependencies. Open http://127.0.0.1:3010 and create “Review paper robot”, priority 2. Use fictional data only.

  4. 4

    Visit /readyz in the browser: release identifies this run. Stop with Ctrl+C, run the same command and find the mission again. Cargo.toml describes the project; target contains the executable; missions.db holds the data that must survive.

  5. 5

    Fill REPORT.md with OS, versions, command and observed result. Do not record a prediction as an execution. If it fails, record the message without personal names or private paths and revisit setup.

From reasoning to execution

The core path runs on your computer with fictional data. Podman, Quadlet and Caddy are optional extensions; no domain purchase or cloud subscription is needed. This lab is not ready for public writes.

Read the steps before running anything. The commands below are a reference; README.md explains your OS syntax and LAB.md contains the sequence. The site does not run these commands for you.

cargo test --locked
cargo run --locked -- serve
My evidence record

Ask someone else, or use a new session, to follow your README. Record one instruction you clarified and the preserved mission. Do not share a real database.

Separate prediction, execution and observed result. Record “not executed” when the environment is missing. Site progress does not validate real deployment or grant professional certification.

My files and GitHub

Official links and next step

✦
YOUR MISSION

Run the kit, create a fictional mission and distinguish source, executable and data.

Now it's your turn

Discovery workshop

Decide using evidence

The repository has src and Cargo.lock. You created 3 missions after downloading. A colleague received only the repository files.
Build your answers and check when you are ready.
A moment to understand

What demonstrates a reproducible handoff?

I need a hint

Source lets you rebuild the program; it does not include created missions. Evidence combines instructions, versions and an observation after restart.

Loading your journey…

Take it with you

Ask someone else, or use a new session, to follow your README. Record one instruction you clarified and the preserved mission. Do not share a real database.

At your own pace

My files and GitHub

Every lesson can become your own record: code, notes or a practice plan. Saving a file to GitHub is optional and does not change your XP.

Student guide

The editor and downloads open when this lesson is available to your account. Check access below or return to the track map.

Checking your access to this lesson…

Rullstpetbot

AI can make mistakes. Check the lesson material.