Rullst AcademyRullst Academy/Lesson
Applications with Rullst I · Lesson 02 / 14

One folder, versions and a first run

An application must work beyond its author’s machine.

Learning paths16 min

Let's discover together

  1. 1

    Install Rust using your system’s track. The kit uses Rust 1.96+ and Rullst =12.1.1. Open a terminal in the folder containing Cargo.toml. Run rustc --version and cargo --version; a terminal opened before installation may need reopening.

  2. 2

    Cargo.toml declares dependencies; Cargo.lock records resolved versions. Run cargo test --locked and cargo run --locked. The first build downloads dependencies and can take time. --locked prevents lockfile updates; --offline works only when dependencies are cached.

  3. 3

    Open http://127.0.0.1:3010. The program listens only on this machine and creates missions.db in the current directory. Ctrl+C stops it. If the port is busy, stop only the test instance you started; do not terminate unknown processes.

  4. 4

    Inspect src/main.rs, src/routes.rs, src/store.rs and web/. The cargo-rullst CLI is optional: this kit is already a Cargo project. Pinning versions helps reproduce results but does not guarantee freedom from vulnerabilities; future updates need review and tests.

Your application workbench

The kit includes a complete app to investigate and modify. The excerpt below explains this step; the editor contains the indicated file. Rullst Academy does not compile or run this server in your browser.

File to study and modify

NOTES.md

rustc --version
cargo test --locked
cargo run --locked
# http://127.0.0.1:3010

Extract the kit to a new folder and open a terminal beside Cargo.toml. Use Rust 1.96+; the first build may download dependencies and take time. Then open http://127.0.0.1:3010. Stop with Ctrl+C and run again after editing.

cargo test --locked
cargo run --locked
My files and GitHub

Download your draft and replace the indicated file in your extracted copy. The editor saves one file in this browser; your account saves assessments and XP. The ZIP excludes your edits. GitHub sends only the confirmed file; use Git manually for the whole app, excluding databases, backups and secrets.

Official links and next step

✦
YOUR MISSION

Run the kit and explain the manifest, lockfile and current directory.

Now it's your turn

Discovery workshop

Decide before running

Run the kit and explain the manifest, lockfile and current directory.
Build your answers and check when you are ready.
A moment to understand

Why ship Cargo.lock with this application?

I need a hint

The lockfile supports reproducibility; data and security review have different roles.

Loading your journey…

Take it with you

Record your system, versions and command. Close and run again in the same folder. Explain where the database is and why another folder can show a different list.

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.