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

Build an identifiable release

A lockfile helps select the same dependencies. It does not turn a Windows executable into a Linux executable.

Learning paths30 min

Let's discover together

  1. 1

    Run rustc -Vv and cargo -V. Record host and version in the report. x86_64 and aarch64 are architectures; Windows, Linux and macOS also have different formats and libraries.

  2. 2

    Check Rullst =12.1.1 in Cargo.toml and resolved versions in Cargo.lock. Run cargo build --release --locked. If the lockfile needs to change, --locked stops instead of silently rewriting it.

  3. 3

    Stop any running kit server before starting the release binary. On Windows use . arget eleasemission-board.exe serve; on Linux/macOS, ./target/release/mission-board serve. Open /readyz and check the chosen label.

  4. 4

    You declare the name lesson-v1; alone it does not prove which bytes were used. Also record the binary SHA-256 using the README command. A hash identifies bytes; it is not a producer signature.

  5. 5

    Keep rebuild instructions, not a promise of identical bytes on every system. Do not copy an .exe to Linux expecting the same command to work. Cross-compilation needs additional tooling.

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.

rustc -Vv
cargo -V
cargo build --release --locked
My evidence record

Deliver a real build record with versions, host, command, hash and result. Explain what information is missing before sending it to another architecture.

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

Build with locked dependencies and record OS, architecture and reproducibility limits.

Now it's your turn

Discovery workshop

Decide using evidence

Cargo.lock changed without review and the target uses another architecture. Separate these two problems.
Build your answers and check when you are ready.
A moment to understand

Is a Windows x86_64 build ready for Linux ARM64?

I need a hint

The lockfile fixes dependency resolution. Platform, compiler and libraries remain part of the build environment.

Loading your journey…

Take it with you

Deliver a real build record with versions, host, command, hash and result. Explain what information is missing before sending it to another architecture.

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.