Skip to content
apsideslabsPublic

About

A Termux and Linux command-line course for your phone: 66 lessons, 105 documented tools, and a real shell beside every lesson. Static, no backend.

Topics

Resources

Code of conduct

Contributing

Security policy

Stars

1 star

Watchers

0 watching

Forks

Repository files navigation

Learmux: learn the Linux command line on your phone

A Termux and Linux command-line course, with a real shell in the page.

Live site Deploy License Node PRs welcome

Lessons Tracks Tools Glossary Challenges

Read the course · Try the sandbox · Report a problem · Contribute


Most command-line courses tell you to run something and leave you to open a terminal. Learmux puts the terminal beside the lesson, seeded with the files that lesson talks about, so the command you are reading is the command you can type.

The course is written for a phone. Termux is a real Linux userland for Android, and everything here assumes it: the paths, the package manager, the two editors you actually have, and the fact that you are reading on a screen the size of a hand.

$ pwd
/data/data/com.termux/files/home
$ grep -c GET access.log
6

No backend, no account, no tracking. The site builds to static files.

What is in it

66 lessons across 12 tracks, in a prerequisite order 66 practice sets: 261 questions, 66 graded output tasks
A shell on every lesson page, seeded with that lesson's files 105 tools documented, with flags, examples and a copy button
392 glossary terms across six subjects, linked to lessons 18 challenges: 12 in-browser labs and 6 Termux CTF
6 calculators that run offline A certificate you can download as SVG or PNG

The course

Twelve tracks, meant to be read in order. Each track assumes the ones above it.

# Track Level Lessons
1 Foundations Beginner 8
2 The shell in practice Intermediate 8
3 Python you can run here Beginner 5
4 Networking and the internet Intermediate 5
5 Security fundamentals Intermediate 7
6 Reconnaissance and assessment Intermediate 5
7 Web and application security Intermediate 5
8 Cryptography in practice Intermediate 5
9 Defence and monitoring Intermediate 5
10 Utilities you build yourself Intermediate 6
11 Projects Advanced 3
12 Working in security Intermediate 4

How it works

Everything runs in the browser. There is no server to call, so the shell, the grading, the progress and the certificate all live in the page.

flowchart LR
    subgraph build["at build time"]
        MDX["lessons<br/>MDX"] --> ASTRO["Astro<br/>static output"]
        DATA["tools, glossary,<br/>practice, challenges"] --> ASTRO
        ASTRO --> HTML["320 static pages"]
    end

    subgraph browser["in the browser"]
        HTML --> PAGE["lesson page"]
        HTML --> TERM["terminal"]
        PAGE --> SB["sandbox<br/>seeded from this lesson"]
        TERM --> SH["shell engine"]
        SB --> SH
        SH --> VFS[("virtual<br/>filesystem")]
        SH --> CMD["105 commands"]
        PAGE --> GRADE["practice grading"]
        PAGE --> PROG[("localStorage<br/>progress")]
    end

    HTML --> PAGES["GitHub Pages"]
Loading

A command goes in, the engine parses it, the command acts on the virtual filesystem, and the output comes back. Nothing leaves the page.

sequenceDiagram
    autonumber
    actor L as Learner
    participant T as Terminal UI
    participant S as Shell engine
    participant F as Virtual FS

    L->>T: git status
    T->>S: runLine("git status")
    S->>S: parse, resolve git
    S->>F: read .git/index.json
    F-->>S: staged tree
    S->>F: walk working tree
    F-->>S: files
    S-->>T: "On branch main ..."
    T-->>L: output + prompt
Loading

What is verified before it deploys

Every push runs the same gate. It is not decoration: each step has caught a real defect in this repository.

flowchart TD
    PUSH["push to main"] --> V["validate content<br/>rules, slugs, order, seeds"]
    V --> E["test the shell engine"]
    E --> U["test the calculators"]
    U --> PR["grade every practice task<br/>runs the real command"]
    PR --> B["build"]
    B --> L["validate every link<br/>and every og:image"]
    L --> TV["test the validator itself"]
    TV --> D["deploy to Pages"]

    style V fill:#1c1b27,color:#fff
    style PR fill:#1c1b27,color:#fff
    style L fill:#1c1b27,color:#fff
Loading

The practice step is the unusual one. Each of the 66 output tasks is run for real in a throwaway home directory and graded against its own rules, so a task that cannot be completed fails the build rather than reaching a learner.

Quick start

git clone https://github.com/apsideslabs/Learmux.git
cd Learmux
npm install
npm run dev          # http://localhost:4321/Learmux/

Node 20 (there is a .nvmrc). No environment variables, no database, no services to start.

Script What it does
npm run dev Local dev server with hot reload
npm run build Build the static site to dist/
npm run validate Check content rules, links and the built output
npm test The shell engine: parsing, commands, filesystem, git
npm run test:practice Run and grade every practice task for real
npm run test:utilities The calculator logic
npm run test:validator Prove the validator still catches what it should
npm run generate:thumbs Redraw the lesson thumbnails
npm run generate:og Rasterise the social images from those thumbnails

Project structure

src/
├── content/tutorials/     66 lessons, one MDX file each; the filename is the URL
├── data/
│   ├── tools/             105 documented commands, grouped by subject
│   ├── glossary/          392 terms across six subjects
│   ├── practice/          66 practice sets: questions and output tasks
│   └── challenges.json    12 in-browser challenges
├── lib/
│   ├── shell.ts           parse and dispatch
│   ├── commands.ts        105 commands
│   ├── fs.ts              the virtual filesystem
│   ├── git.ts             a small, real git
│   ├── lesson-sandbox.ts  per-lesson seeds
│   ├── practice-grade.ts  output grading rules
│   └── progress.ts        localStorage progress
├── pages/                 routes: course, learn, practice, tools, glossary,
│                          ctf, challenges, utilities, tags, profile, search
├── components/            terminal, sandbox, practice widgets, certificate
└── styles/                the palette and the layout
scripts/
├── validate-content.mjs   the content gate
├── test-practice.mjs      runs and grades every task
├── test-engine.mjs        the shell tests
└── generate-*.mjs         thumbnails, og images, challenges
docs/
├── banner.svg             the image at the top of this file
└── challenge-format.md    how a challenge is defined

Contributing

Corrections to lesson content are the most useful thing you can send, and they are the easiest to review. Read CONTRIBUTING.md first: it lists the rules the build actually enforces, so you do not have to guess.

Everything is checked by npm run validate and npm test, so you can be sure a pull request passes before you open it.

What this is not

Being clear about the edges is more useful than overselling them.

  • The shell is not a real shell. It is 105 commands over a virtual filesystem. apt install will not work, and nothing touches your device. Where it cannot match the real tool it says so, and the commands that matter (grep, sed, git) match the real ones closely.
  • The sandbox git has no branches or remotes. It has the daily loop. The lesson says so in the text.
  • There are no publication dates, because there is no honest source for them. The feed carries none for the same reason.
  • Progress is per browser. It lives in localStorage; the certificate is a record of what you marked done, not a proctored credential.

License

MIT. See LICENSE.


Apsides Labs

Designed and built by Apsides Labs.

About

A Termux and Linux command-line course for your phone: 66 lessons, 105 documented tools, and a real shell beside every lesson. Static, no backend.

Topics

Resources

Code of conduct

Contributing

Security policy

Stars

1 star

Watchers

0 watching

Forks

Releases

Packages

Contributors

Languages