Hands-on lesson

Give AI Your Own Documents

Load your own text files, split them into searchable chunks, and retrieve relevant context without a vector database.

13 minFree Core9 Hands-On AI Lessonsbeginner

What you'll build

Three learner-owned documents

A deterministic chunking function

Relevant text retrieved for a query

docs/ folder

*.txt files

→

load_chunks()

split("\n\n")

→

Chunks

(filename, text)

→

search()

keyword overlap

→

Best chunk

handbook.txt

File removed

handbook.missing

→

load_chunks()

glob *.txt

→

Worse result

irrelevant chunk

→

Debug

find docs -type f

Check

Before You Build

2 quick questions. This is diagnostic only — it does not block the lesson.

1 / 4Core

Does the model automatically know local private files?

Local files must be retrieved and supplied as context.

2 / 4Core

Why retain the source filename with each chunk?

Source names let the final answer cite evidence.

understand

build

break

debug

improve

deploy

Mission

Load your own text files, split them into searchable chunks, and retrieve relevant context without a vector database.

Understand

A model does not automatically know private files. Retrieval selects useful document content first; that selected context can then be supplied to the model.

Build

What you're doing

Create three text documents and documents.py, save each file, then run the search.

Why it matters

The learner-owned files become inspectable evidence that retrieval can select before generation.

Create, open, paste, and save~/enjyra-free-ai/docs/company.txt

Where to work VS Code FileLanguage text

Create and open the fileRun this from ~/enjyra-free-ai.

mkdir -p docs
touch docs/company.txt
code docs/company.txt

mkdir -p docs
touch docs/company.txt
code docs/company.txt

New-Item -ItemType Directory -Force -Path "docs" | Out-Null
if (-not (Test-Path "docs\company.txt")) { New-Item -ItemType File -Path "docs\company.txt" | Out-Null }
code "docs\company.txt"

Before You Run

Your terminal is open in ~/enjyra-free-ai.
Visual Studio Code is installed; the optional code shell command is available, or you can open the file manually.

Why You're Running This

docs/company.txt is the project’s text file at ~/enjyra-free-ai/docs/company.txt. It must exist before you can paste the supplied content. The commands create its folder when needed, create the file, and open it in VS Code; the next stage tells you what to paste and reminds you to save it.

Command Breakdown

mkdir -p / New-Item Directory: Creates the requested folder and any missing parent folders without failing when it already exists.
touch / New-Item File: Creates an empty file at the requested path without requiring code to exist first.
code: Opens the file or folder in Visual Studio Code from the terminal.

Expected Result

docs/
└── company.txt

docs/company.txt exists and is ready for the supplied content.

What Changed

Beforedocs/company.txt may not exist yet, or may still contain its previous content.

Afterdocs/company.txt now exists in the lesson workspace and is ready for the next instruction.

Verify It

macOSls -l docs/company.txt

Linuxls -l docs/company.txt

Windows PowerShellGet-Item "docs\company.txt"

Confirm the file exists at the expected path.

If It Fails

Check that the terminal is in the lesson project, the path spelling is exact, and VS Code is installed. If the code command is unavailable, use File → Open Folder in VS Code.

If code is unavailable, open VS Code, choose File → Open Folder, select enjyra-free-ai, then create docs/company.txt in the Explorer.

Paste this contentCopy the complete block into docs/company.txt.

ENJYRA teaches practical AI engineering through build, break, debug, fix, and verify.

Save before continuing: press Cmd + S on macOS or Ctrl + S on Linux and Windows.

Verify the saved fileThe command should print the content you just saved.

cat docs/company.txt

cat docs/company.txt

Get-Content "docs\company.txt"

Before You Run

Your terminal is open in ~/enjyra-free-ai.

Why You're Running This

Reading docs/company.txt back from disk proves that the text content was saved at the correct path, rather than remaining only in an unsaved editor tab.

Command Breakdown

cat / Get-Content: Reads the saved file and prints its contents so you can verify it.

Expected Result

The terminal prints the complete content you pasted into docs/company.txt.

What Changed

BeforeThe current state has not yet been checked.

AfterNo persistent state changed; the command printed evidence you can compare with the expected result.

Verify It

macOScat docs/company.txt

Linuxcat docs/company.txt

Windows PowerShellGet-Content "docs\company.txt"

Run the command and compare its output with the Expected Result block.

If It Fails

Save the file, confirm the filename and capitalisation, and check the current folder with pwd on macOS/Linux or Get-Location on Windows.

If it fails

Check that your terminal is in ~/enjyra-free-ai, the filename and capitalisation match exactly, and the file was saved. Use pwd on macOS/Linux or Get-Location on Windows to check your current folder.

Create, open, paste, and save~/enjyra-free-ai/docs/product.txt

Where to work VS Code FileLanguage text

Create and open the fileRun this from ~/enjyra-free-ai.

mkdir -p docs
touch docs/product.txt
code docs/product.txt

mkdir -p docs
touch docs/product.txt
code docs/product.txt

New-Item -ItemType Directory -Force -Path "docs" | Out-Null
if (-not (Test-Path "docs\product.txt")) { New-Item -ItemType File -Path "docs\product.txt" | Out-Null }
code "docs\product.txt"

Before You Run

Your terminal is open in ~/enjyra-free-ai.
Visual Studio Code is installed; the optional code shell command is available, or you can open the file manually.

Why You're Running This

docs/product.txt is the project’s text file at ~/enjyra-free-ai/docs/product.txt. It must exist before you can paste the supplied content. The commands create its folder when needed, create the file, and open it in VS Code; the next stage tells you what to paste and reminds you to save it.

Command Breakdown

mkdir -p / New-Item Directory: Creates the requested folder and any missing parent folders without failing when it already exists.
touch / New-Item File: Creates an empty file at the requested path without requiring code to exist first.
code: Opens the file or folder in Visual Studio Code from the terminal.

Expected Result

docs/
└── product.txt

docs/product.txt exists and is ready for the supplied content.

What Changed

Beforedocs/product.txt may not exist yet, or may still contain its previous content.

Afterdocs/product.txt now exists in the lesson workspace and is ready for the next instruction.

Verify It

macOSls -l docs/product.txt

Linuxls -l docs/product.txt

Windows PowerShellGet-Item "docs\product.txt"

Confirm the file exists at the expected path.

If It Fails

Check that the terminal is in the lesson project, the path spelling is exact, and VS Code is installed. If the code command is unavailable, use File → Open Folder in VS Code.

If code is unavailable, open VS Code, choose File → Open Folder, select enjyra-free-ai, then create docs/product.txt in the Explorer.

Paste this contentCopy the complete block into docs/product.txt.

ENJYRA Free includes nine core hands-on lessons and three optional cloud bonus labs.

Save before continuing: press Cmd + S on macOS or Ctrl + S on Linux and Windows.

Verify the saved fileThe command should print the content you just saved.

cat docs/product.txt

cat docs/product.txt

Get-Content "docs\product.txt"

Before You Run

Your terminal is open in ~/enjyra-free-ai.

Why You're Running This

Reading docs/product.txt back from disk proves that the text content was saved at the correct path, rather than remaining only in an unsaved editor tab.

Command Breakdown

cat / Get-Content: Reads the saved file and prints its contents so you can verify it.

Expected Result

The terminal prints the complete content you pasted into docs/product.txt.

What Changed

BeforeThe current state has not yet been checked.

AfterNo persistent state changed; the command printed evidence you can compare with the expected result.

Verify It

macOScat docs/product.txt

Linuxcat docs/product.txt

Windows PowerShellGet-Content "docs\product.txt"

Run the command and compare its output with the Expected Result block.

If It Fails

Save the file, confirm the filename and capitalisation, and check the current folder with pwd on macOS/Linux or Get-Location on Windows.

If it fails

Create, open, paste, and save~/enjyra-free-ai/docs/handbook.txt

Where to work VS Code FileLanguage text

Create and open the fileRun this from ~/enjyra-free-ai.

mkdir -p docs
touch docs/handbook.txt
code docs/handbook.txt

mkdir -p docs
touch docs/handbook.txt
code docs/handbook.txt

New-Item -ItemType Directory -Force -Path "docs" | Out-Null
if (-not (Test-Path "docs\handbook.txt")) { New-Item -ItemType File -Path "docs\handbook.txt" | Out-Null }
code "docs\handbook.txt"

Before You Run

Your terminal is open in ~/enjyra-free-ai.
Visual Studio Code is installed; the optional code shell command is available, or you can open the file manually.

Why You're Running This

docs/handbook.txt is the project’s text file at ~/enjyra-free-ai/docs/handbook.txt. It must exist before you can paste the supplied content. The commands create its folder when needed, create the file, and open it in VS Code; the next stage tells you what to paste and reminds you to save it.

Command Breakdown

mkdir -p / New-Item Directory: Creates the requested folder and any missing parent folders without failing when it already exists.
touch / New-Item File: Creates an empty file at the requested path without requiring code to exist first.
code: Opens the file or folder in Visual Studio Code from the terminal.

Expected Result

docs/
└── handbook.txt

docs/handbook.txt exists and is ready for the supplied content.

What Changed

Beforedocs/handbook.txt may not exist yet, or may still contain its previous content.

Afterdocs/handbook.txt now exists in the lesson workspace and is ready for the next instruction.

Verify It

macOSls -l docs/handbook.txt

Linuxls -l docs/handbook.txt

Windows PowerShellGet-Item "docs\handbook.txt"

Confirm the file exists at the expected path.

If It Fails

Check that the terminal is in the lesson project, the path spelling is exact, and VS Code is installed. If the code command is unavailable, use File → Open Folder in VS Code.

If code is unavailable, open VS Code, choose File → Open Folder, select enjyra-free-ai, then create docs/handbook.txt in the Explorer.

Paste this contentCopy the complete block into docs/handbook.txt.

Employees may carry over up to five unused holiday days into the next year.

Save before continuing: press Cmd + S on macOS or Ctrl + S on Linux and Windows.

Verify the saved fileThe command should print the content you just saved.

cat docs/handbook.txt

cat docs/handbook.txt

Get-Content "docs\handbook.txt"

Before You Run

Your terminal is open in ~/enjyra-free-ai.

Why You're Running This

Reading docs/handbook.txt back from disk proves that the text content was saved at the correct path, rather than remaining only in an unsaved editor tab.

Command Breakdown

cat / Get-Content: Reads the saved file and prints its contents so you can verify it.

Expected Result

The terminal prints the complete content you pasted into docs/handbook.txt.

What Changed

BeforeThe current state has not yet been checked.

AfterNo persistent state changed; the command printed evidence you can compare with the expected result.

Verify It

macOScat docs/handbook.txt

Linuxcat docs/handbook.txt

Windows PowerShellGet-Content "docs\handbook.txt"

Run the command and compare its output with the Expected Result block.

If It Fails

Save the file, confirm the filename and capitalisation, and check the current folder with pwd on macOS/Linux or Get-Location on Windows.

If it fails

Create, open, paste, and save~/enjyra-free-ai/app/documents.py

Where to work VS Code FileLanguage python

Create and open the fileRun this from ~/enjyra-free-ai.

mkdir -p app
touch app/documents.py
code app/documents.py

mkdir -p app
touch app/documents.py
code app/documents.py

New-Item -ItemType Directory -Force -Path "app" | Out-Null
if (-not (Test-Path "app\documents.py")) { New-Item -ItemType File -Path "app\documents.py" | Out-Null }
code "app\documents.py"

Before You Run

Your terminal is open in ~/enjyra-free-ai.
Python 3 is installed; activate .venv first when the lesson has already created it.
Visual Studio Code is installed; the optional code shell command is available, or you can open the file manually.

Why You're Running This

app/documents.py is the project’s python file at ~/enjyra-free-ai/app/documents.py. It must exist before you can paste the supplied content. The commands create its folder when needed, create the file, and open it in VS Code; the next stage tells you what to paste and reminds you to save it.

Command Breakdown

mkdir -p / New-Item Directory: Creates the requested folder and any missing parent folders without failing when it already exists.
touch / New-Item File: Creates an empty file at the requested path without requiring code to exist first.
code: Opens the file or folder in Visual Studio Code from the terminal.

Expected Result

app/
└── documents.py

app/documents.py exists and is ready for the supplied content.

What Changed

Beforeapp/documents.py may not exist yet, or may still contain its previous content.

Afterapp/documents.py now exists in the lesson workspace and is ready for the next instruction.

Verify It

macOSls -l app/documents.py

Linuxls -l app/documents.py

Windows PowerShellGet-Item "app\documents.py"

Confirm the file exists at the expected path.

If It Fails

Check that the terminal is in the lesson project, the path spelling is exact, and VS Code is installed. If the code command is unavailable, use File → Open Folder in VS Code.

If code is unavailable, open VS Code, choose File → Open Folder, select enjyra-free-ai, then create app/documents.py in the Explorer.

Paste this contentCopy the complete block into app/documents.py.

from pathlib import Path

def load_chunks(folder: Path) -> list[tuple[str, str]]:
    chunks = []
    for file in sorted(folder.glob("*.txt")):
        for paragraph in file.read_text().split("\n\n"):
            if paragraph.strip():
                chunks.append((file.name, paragraph.strip()))
    return chunks

def search(chunks, query: str):
    words = set(query.lower().split())
    return sorted(chunks, key=lambda item: len(words & set(item[1].lower().split())), reverse=True)

if __name__ == "__main__":
    results = search(load_chunks(Path("docs")), "holiday carry over")
    print(results[0][0])
    print(results[0][1])

Save before continuing: press Cmd + S on macOS or Ctrl + S on Linux and Windows.

Verify the saved fileThe command should print the content you just saved.

cat app/documents.py

cat app/documents.py

Get-Content "app\documents.py"

Before You Run

Your terminal is open in ~/enjyra-free-ai.
Python 3 is installed; activate .venv first when the lesson has already created it.

Why You're Running This

Reading app/documents.py back from disk proves that the python content was saved at the correct path, rather than remaining only in an unsaved editor tab.

Command Breakdown

cat / Get-Content: Reads the saved file and prints its contents so you can verify it.

Expected Result

The terminal prints the complete content you pasted into app/documents.py.

What Changed

BeforeThe current state has not yet been checked.

AfterNo persistent state changed; the command printed evidence you can compare with the expected result.

Verify It

macOScat app/documents.py

Linuxcat app/documents.py

Windows PowerShellGet-Content "app\documents.py"

Run the command and compare its output with the Expected Result block.

If It Fails

Save the file, confirm the filename and capitalisation, and check the current folder with pwd on macOS/Linux or Get-Location on Windows.

If it fails

TerminalChoose macOS, Linux, Windows, or Explain

Where to run Terminal or VS Code TerminalWorking directory ~/enjyra-free-ai

What to run

cd ~/enjyra-free-ai && . .venv/bin/activate && python3 app/documents.py

cd ~/enjyra-free-ai && . .venv/bin/activate && python3 app/documents.py

Set-Location $HOME\enjyra-free-ai
.\.venv\Scripts\Activate.ps1
py app\documents.py

Before You Run

Your terminal is open in ~/enjyra-free-ai.
Python 3 is installed; activate .venv first when the lesson has already created it.

Why You're Running This

Running the program proves that the saved code and its local dependencies work together.

Command Breakdown

cd / Set-Location: Changes the terminal’s current working directory before the next command runs.
.: Runs the . tool with the shown arguments to complete this lesson step.
python: Runs the selected Python module or script with the supplied arguments.
activate: Makes the project’s virtual environment the active Python environment for this terminal session.
&&: Runs the next command only when the previous command succeeds.

Expected Result

handbook.txt
Employees may carry over up to five unused holiday days...

The simple search returns the relevant learner document.

What Changed

BeforeThe saved program has not yet been executed for this verification step.

AfterThe program ran and produced output or started the local process described by the lesson.

Verify It

macOSInspect the command output shown above.

LinuxInspect the command output shown above.

Windows PowerShellInspect the command output shown above.

Continue only when the observed result matches the Expected Result block.

If It Fails

No such file or directory → verify the current folder and the path spelling.
Permission denied → work inside your own lesson folder and confirm it is writable.

What you should see

handbook.txt
Employees may carry over up to five unused holiday days...

Success looks like: The simple search returns the relevant learner document.

If it fails

command not found → verify the required tool is installed and reopen the terminal.
No such file or directory → check your current folder with pwd or Get-Location.
Permission denied → confirm the lesson workspace is writable.

What changed

docs/ contains three saved sources and app/documents.py can search them.

Break

TerminalChoose macOS, Linux, Windows, or Explain

Where to run Terminal or VS Code TerminalWorking directory ~/enjyra-free-ai

What to run

cd ~/enjyra-free-ai && mv docs/handbook.txt docs/handbook.missing && . .venv/bin/activate && python3 app/documents.py

cd ~/enjyra-free-ai && mv docs/handbook.txt docs/handbook.missing && . .venv/bin/activate && python3 app/documents.py

Set-Location $HOME\enjyra-free-ai
Move-Item docs\handbook.txt docs\handbook.missing
.\.venv\Scripts\Activate.ps1
py app\documents.py

Before You Run

Your terminal is open in ~/enjyra-free-ai.
Python 3 is installed; activate .venv first when the lesson has already created it.

Why You're Running This

Running the program proves that the saved code and its local dependencies work together.

Command Breakdown

cd / Set-Location: Changes the terminal’s current working directory before the next command runs.
mv: Runs the mv tool with the shown arguments to complete this lesson step.
.: Runs the . tool with the shown arguments to complete this lesson step.
python: Runs the selected Python module or script with the supplied arguments.
Move-Item: Runs the Move-Item tool with the shown arguments to complete this lesson step.
activate: Makes the project’s virtual environment the active Python environment for this terminal session.
&&: Runs the next command only when the previous command succeeds.

Expected Result

<irrelevant result>

Removing the relevant source makes retrieval quality visibly worse.

What Changed

BeforeThe saved program has not yet been executed for this verification step.

AfterThe program ran and produced output or started the local process described by the lesson.

Verify It

macOSInspect the command output shown above.

LinuxInspect the command output shown above.

Windows PowerShellInspect the command output shown above.

Continue only when the observed result matches the Expected Result block.

If It Fails

No such file or directory → verify the current folder and the path spelling.
Permission denied → work inside your own lesson folder and confirm it is writable.

What you should see

<irrelevant result>

Success looks like: Removing the relevant source makes retrieval quality visibly worse.

If it fails

Debug

TerminalChoose macOS, Linux, Windows, or Explain

Where to run Terminal or VS Code TerminalWorking directory ~/enjyra-free-ai

What to run

cd ~/enjyra-free-ai && find docs -maxdepth 1 -type f -print

cd ~/enjyra-free-ai && find docs -maxdepth 1 -type f -print

Set-Location $HOME\enjyra-free-ai
Get-ChildItem docs -File | Select-Object -ExpandProperty Name

Before You Run

Your terminal is open in ~/enjyra-free-ai.

Why You're Running This

This command completes the “this step” step and produces the state needed by the next instruction.

Command Breakdown

cd / Set-Location: Changes the terminal’s current working directory before the next command runs.
find: Runs the find tool with the shown arguments to complete this lesson step.
ls / Get-Item: Inspects the requested file or folder without modifying it.
&&: Runs the next command only when the previous command succeeds.

Expected Result

company.txt
product.txt

The file inventory reveals the missing handbook source.

What Changed

BeforeThe action shown by this card has not yet been completed or verified.

AfterThe command has completed and the next lesson step has the state it needs.

Verify It

macOSInspect the command output shown above.

LinuxInspect the command output shown above.

Windows PowerShellInspect the command output shown above.

Continue only when the observed result matches the Expected Result block.

If It Fails

No such file or directory → verify the current folder and the path spelling.
Permission denied → work inside your own lesson folder and confirm it is writable.

What you should see

company.txt
product.txt

Success looks like: The file inventory reveals the missing handbook source.

If it fails

Improve

This keyword overlap is deliberately small. Lesson 7 uses the retrieved chunk as grounding context and adds honest refusal.

Verify

TerminalChoose macOS, Linux, Windows, or Explain

Where to run Terminal or VS Code TerminalWorking directory ~/enjyra-free-ai

What to run

cd ~/enjyra-free-ai && mv docs/handbook.missing docs/handbook.txt && . .venv/bin/activate && python3 app/documents.py

cd ~/enjyra-free-ai && mv docs/handbook.missing docs/handbook.txt && . .venv/bin/activate && python3 app/documents.py

Set-Location $HOME\enjyra-free-ai
Move-Item docs\handbook.missing docs\handbook.txt
.\.venv\Scripts\Activate.ps1
py app\documents.py

Before You Run

Your terminal is open in ~/enjyra-free-ai.
Python 3 is installed; activate .venv first when the lesson has already created it.

Why You're Running This

Running the program proves that the saved code and its local dependencies work together.

Command Breakdown

cd / Set-Location: Changes the terminal’s current working directory before the next command runs.
mv: Runs the mv tool with the shown arguments to complete this lesson step.
.: Runs the . tool with the shown arguments to complete this lesson step.
python: Runs the selected Python module or script with the supplied arguments.
Move-Item: Runs the Move-Item tool with the shown arguments to complete this lesson step.
activate: Makes the project’s virtual environment the active Python environment for this terminal session.
&&: Runs the next command only when the previous command succeeds.

Expected Result

handbook.txt
Employees may carry over...

Restoring the source restores the correct result.

What Changed

BeforeThe saved program has not yet been executed for this verification step.

AfterThe program ran and produced output or started the local process described by the lesson.

Verify It

macOSInspect the command output shown above.

LinuxInspect the command output shown above.

Windows PowerShellInspect the command output shown above.

Continue only when the observed result matches the Expected Result block.

If It Fails

No such file or directory → verify the current folder and the path spelling.
Permission denied → work inside your own lesson folder and confirm it is writable.

What you should see

handbook.txt
Employees may carry over...

Success looks like: Restoring the source restores the correct result.

If it fails

Challenge

Repeat the verification from a fresh terminal and explain which observable signal proves each dependency is healthy.

Ship

A transparent document loader and retrieval step you can inspect without hidden infrastructure.

Next Step

Continue to Lesson 07: Build a Tiny RAG Application.

03 · Prerequisites

Before You Start the Lab

Confirm your machine has everything required for this lesson. Continue only when the verification commands succeed.

This lesson needs

DockerPython 3VS Code — requiredInternet: only for first-time pullsGPU: optional

ENJYRA Lab Setup completed

Prior lesson 05 completed

Docker Desktop or Docker Engine running

Terminal access

Python 3 installed

Visual Studio Code — required for this guided lab

Disk10 GB free if the runtime or model is not cached

Memory8 GB recommended

GPUOptional

InternetRequired only for uncached dependencies or images

Docker setup

Docker CLI

Docker Engine

Test container

Docker not installed? Show setup instructions ▾

Check your Mac's chip architecture (Apple Silicon vs Intel) before downloading.
Where to runTerminalPlatformmacOS
COMMAND
```
uname -m
```
Expected output"arm64" (Apple Silicon) or "x86_64" (Intel)
If error
If nothing prints, open Terminal from Applications → Utilities and try again.
Download Docker Desktop for your chip from docs.docker.com/desktop/setup/install/mac-install and open the downloaded .dmg, then drag Docker to Applications.
Launch Docker Desktop from Applications and wait for the whale icon in the menu bar to show "Docker Desktop is running".
Verify the CLI is installed.
Where to runTerminalPlatformmacOS
COMMAND
```
docker --version
```
Expected outputDocker version 2x.x.x, build xxxxxxx
If error
If “command not found”, reopen Terminal after installing so your PATH refreshes, or reinstall Docker Desktop.
Verify the engine is actually running (not just installed).
Where to runTerminalPlatformmacOS
COMMAND
```
docker info
```
Expected outputA block of server information, including Server Version and Containers
If error
If it says “Cannot connect to the Docker daemon”, open Docker Desktop and wait for the whale icon to stop animating.
Run a real test container end-to-end.
Where to runTerminalPlatformmacOS
COMMAND
```
docker run --rm hello-world
```
Expected output"Hello from Docker!" followed by an explanation of what happened
If error
If the image can't be pulled, check your internet connection; this is the only step that needs it.

Download Docker Desktop for Windows from docs.docker.com/desktop/setup/install/windows-install and run the installer. Docker Desktop will guide you through any compatible Windows backend requirement; this lesson does not require a WSL terminal.
If the installer asks you to enable a Windows feature or restart, follow that prompt and finish the Docker Desktop setup before continuing.
Start Docker Desktop from the Start menu and wait for the whale icon in the system tray to report "Docker Desktop is running".
Verify the CLI, using PowerShell or the built-in VS Code terminal (not a Bash-syntax terminal).
Where to runPowerShell or VS Code terminalPlatformWindows
COMMAND
```
docker --version
```
Expected outputDocker version 2x.x.x, build xxxxxxx
If error
If “not recognized”, close and reopen your terminal so PATH changes take effect.
Verify the engine is running.
Where to runPowerShell or VS Code terminalPlatformWindows
COMMAND
```
docker info
```
Expected outputA block of server information, including Server Version and Containers
If error
If it can't connect to the daemon, open Docker Desktop, wait until it reports Running, and review Docker Desktop's own Troubleshoot panel.
Run a real test container.
Where to runPowerShell or VS Code terminalPlatformWindows
COMMAND
```
docker run --rm hello-world
```
Expected output"Hello from Docker!" followed by an explanation of what happened
If error
If the pull hangs, check your internet connection and that Docker Desktop shows as running, not starting.

Prefer Docker Engine (not Docker Desktop) on Linux. Follow the official instructions for your distribution at docs.docker.com/engine/install — for Ubuntu specifically, use docs.docker.com/engine/install/ubuntu.
Start and enable the Docker service.
Where to runTerminalPlatformLinux
COMMAND
```
sudo systemctl enable --now docker
```
Expected outputNo output on success
If error
If systemctl isn't available, your distro may use a different init system — check its Docker Engine install page.
Confirm the service is active.
Where to runTerminalPlatformLinux
COMMAND
```
systemctl status docker
```
Expected outputActive: active (running)
If error
If it shows “inactive” or “failed”, re-run the enable command above and check the install steps were completed.
Verify the CLI.
Where to runTerminalPlatformLinux
COMMAND
```
docker --version
```
Expected outputDocker version 2x.x.x, build xxxxxxx
If error
If “command not found”, the Engine install likely didn't finish — re-check the distro-specific install page.
Verify the engine responds.
Where to runTerminalPlatformLinux
COMMAND
```
docker info
```
Expected outputA block of server information, including Server Version and Containers
If error
A permission-denied error here usually means your user isn't in the docker group yet — see the note below rather than running commands as root.
Run a real test container.
Where to runTerminalPlatformLinux
COMMAND
```
docker run --rm hello-world
```
Expected output"Hello from Docker!" followed by an explanation of what happened
If error
If you see a permission error, add your user to the docker group yourself (sudo usermod -aG docker $USER, then log out and back in) — we won't do this for you automatically.

Note: running Docker commands as root or with a global chmod on the socket is not recommended. Add your user to the docker group instead, as shown above.

Before You Run

Install Docker Desktop on macOS or Windows, or Docker Engine/Desktop using the official instructions for your Linux distribution. Start Docker and open Terminal or native Windows PowerShell.

Why Do We Need Docker?

The ENJYRA AWS, Azure, and GCP labs run locally inside Docker containers. No real AWS, Azure, or GCP account is required.

Command Breakdown

docker --version: Confirms the Docker command-line client is installed.
docker info: Asks the Docker Engine for server information, proving it is running and reachable.
docker run --rm hello-world: Runs a small official test container end to end and removes it when finished.

Expected Result

Docker version 2x.x.x
docker info: server details
Hello from Docker!

What Changed

BeforeDocker is not yet confirmed.

AfterDocker CLI and Docker Engine are available to launch the local lab.

Verify It

macOSdocker --version docker info

Linuxdocker --version docker info

Windows PowerShelldocker --version docker info

If It Fails

Open Docker Desktop or start Docker Engine, wait until it reports running, and retry.
Open a new terminal after installation so PATH changes are loaded.
On Linux, follow the official instructions for your distribution rather than assuming Ubuntu commands apply.

Verify your setup

Run each command in your own terminal. This page cannot run commands on your machine, so tick a box only after you see the expected result.

Docker CLIConfirms the Docker command-line client is installed.

COMMAND

docker --version

docker --version

docker --version

Before You Run

Your terminal is open in Any terminal folder.
Docker Desktop or Docker Engine is running.

Why You're Running This

Confirms the Docker command-line client is installed.

Command Breakdown

docker: Runs the docker tool with the shown arguments to complete this lesson step.

Expected Result

A Docker version is printed

What Changed

BeforeThe action shown by this card has not yet been completed or verified.

AfterThe command has completed and the next lesson step has the state it needs.

Verify It

macOSInspect the command output shown above.

LinuxInspect the command output shown above.

Windows PowerShellInspect the command output shown above.

Continue only when the observed result matches the Expected Result block.

If It Fails

Confirm Docker CLI is installed or running, then retry the command in a new terminal.

Expected resultA Docker version is printed

I got the expected result

Docker EngineConfirms Docker is actually running, not only installed.

COMMAND

docker info

docker info

docker info

Before You Run

Your terminal is open in Any terminal folder.
Docker Desktop or Docker Engine is running.

Why You're Running This

Confirms Docker is actually running, not only installed.

Command Breakdown

docker: Runs the docker tool with the shown arguments to complete this lesson step.

Expected Result

Docker server information is returned

What Changed

BeforeThe action shown by this card has not yet been completed or verified.

AfterThe command has completed and the next lesson step has the state it needs.

Verify It

macOSInspect the command output shown above.

LinuxInspect the command output shown above.

Windows PowerShellInspect the command output shown above.

Continue only when the observed result matches the Expected Result block.

If It Fails

Confirm Docker Engine is installed or running, then retry the command in a new terminal.

Expected resultDocker server information is returned

I got the expected result

PythonConfirms Python 3 is installed. On Windows PowerShell use py --version or python --version if python3 is not found.

COMMAND

python3 --version

python3 --version

py --version
# If py is unavailable:
python --version

Before You Run

Your terminal is open in Any terminal folder.
Python 3 is installed; activate .venv first when the lesson has already created it.

Why You're Running This

Confirms Python 3 is installed. On Windows PowerShell use py --version or python --version if python3 is not found.

Command Breakdown

python: Runs the selected Python module or script with the supplied arguments.
py: Runs the py tool with the shown arguments to complete this lesson step.
#: Runs the # tool with the shown arguments to complete this lesson step.

Expected Result

A supported Python 3.x version is printed

What Changed

BeforeThe saved program has not yet been executed for this verification step.

AfterThe program ran and produced output or started the local process described by the lesson.

Verify It

macOSInspect the command output shown above.

LinuxInspect the command output shown above.

Windows PowerShellInspect the command output shown above.

Continue only when the observed result matches the Expected Result block.

If It Fails

Confirm Python is installed or running, then retry the command in a new terminal.

Expected resultA supported Python 3.x version is printed

I got the expected result

Visual Studio CodeOpen Visual Studio Code from your applications. The optional code --version shell command is not required; VS Code works without it.

Expected resultVisual Studio Code opens successfully

Visual Studio Code ready

Ready to start?

Docker CLI verified
Docker Engine running
Python 3 verified
Visual Studio Code ready

Need help with a prerequisite?

Docker not running? Open Docker Desktop or start Docker Engine, then run docker info.

Permission denied? Confirm your account can access the Docker daemon; do not use a global prune.

Port already in use? Use docker ps to identify the container that owns the port.

04 · ENJYRA Lab

Launch the ENJYRA Lab

Start only after the prerequisite checks above are complete.

This button confirms readiness; commands still run in your own terminal.

ENJYRA Lab · 06-documents-v6.0.0

AvailabilityREMOTE VERIFIED

RuntimeDocker + Ollama

Imageenjyra/free-python-labs:06-documents-v6.0.0

PlatformsDocker Desktop · Docker Engine

Architecturelinux/arm64

Start lab

Where to runTerminalWorking directoryAny terminal folderPlatformmacOS · Linux · Windows

COMMAND

docker run --rm --name enjyra-v6-documents-06 enjyra/free-python-labs:06-documents-v6.0.0

docker run --rm --name enjyra-v6-documents-06 enjyra/free-python-labs:06-documents-v6.0.0

docker run --rm --name enjyra-v6-documents-06 enjyra/free-python-labs:06-documents-v6.0.0

Before You Run

Your terminal is open in Any terminal folder.
Docker Desktop or Docker Engine is running.
Python 3 is installed; activate .venv first when the lesson has already created it.

Why You're Running This

Creates and starts the verified ENJYRA lesson container on your machine.

Command Breakdown

docker run: Creates and starts a container from the named image using the supplied ports, environment values, and runtime options.
--rm: Automatically removes the temporary container after it stops.
--name enjyra-v6-documents-06: Assigns a predictable lesson-scoped name so the container can be inspected or removed safely.
enjyra/free-python-labs:06-documents-v6.0.0: Names the verified ENJYRA lesson image and its pinned lesson version.

Expected Result

The lesson container starts successfully.

What Changed

BeforeThe requested local service or lab containers are not yet confirmed running.

AfterThe local service or lab containers are running in the background and can be verified.

Verify It

macOSdocker ps

Linuxdocker ps

Windows PowerShelldocker ps

Confirm the expected container is listed as running or healthy.

If It Fails

Check the current folder, confirm Docker is running when required, and verify the image or script name before retrying.

What this command does Creates and starts the verified ENJYRA lesson container on your machine.

Expected result

The lesson container starts successfully.

If it fails

Check the current folder, confirm Docker is running when required, and verify the image or script name before retrying.

Verify running state

Where to runTerminalWorking directoryAny terminal folderPlatformmacOS · Linux · Windows

COMMAND

docker image inspect enjyra/free-python-labs:06-documents-v6.0.0 --format '{{.Architecture}}'

docker image inspect enjyra/free-python-labs:06-documents-v6.0.0 --format '{{.Architecture}}'

docker image inspect enjyra/free-python-labs:06-documents-v6.0.0 --format '{{.Architecture}}'

Before You Run

Your terminal is open in Any terminal folder.
Docker Desktop or Docker Engine is running.
Python 3 is installed; activate .venv first when the lesson has already created it.

Why You're Running This

Reads the local image metadata and prints only its architecture so you can confirm that the expected ENJYRA image exists.

Command Breakdown

docker image inspect: Reads metadata for the named local image without creating or starting a container.
enjyra/free-python-labs:06-documents-v6.0.0: Identifies the exact ENJYRA image and lesson tag to inspect.
--format: Prints only the requested metadata field instead of the complete image record.

Expected Result

amd64 or arm64

What Changed

BeforeThe current state has not yet been checked.

AfterNo persistent state changed; the command printed evidence you can compare with the expected result.

Verify It

macOSdocker image inspect enjyra/free-python-labs:06-documents-v6.0.0 --format '{{.Architecture}}'

Linuxdocker image inspect enjyra/free-python-labs:06-documents-v6.0.0 --format '{{.Architecture}}'

Windows PowerShelldocker image inspect enjyra/free-python-labs:06-documents-v6.0.0 --format '{{.Architecture}}'

Run the command and compare its output with the Expected Result block.

If It Fails

Confirm the start command completed first, then compare the image, container, port, or script name exactly with this lesson.

What this command does Reads the local image metadata and prints only its architecture so you can confirm that the expected ENJYRA image exists.

Expected result

amd64 or arm64

If it fails

Confirm the start command completed first, then compare the image, container, port, or script name exactly with this lesson.

Reset My Lab

Reset lab

Where to runTerminalWorking directoryAny terminal folderPlatformmacOS · Linux · Windows

COMMAND

docker rm -f enjyra-v6-documents-06 2>/dev/null || true

docker rm -f enjyra-v6-documents-06 2>/dev/null || true

docker rm -f enjyra-v6-documents-06 2>$null

Before You Run

Your terminal is open in Any terminal folder.
Docker Desktop or Docker Engine is running.

Why You're Running This

Returns this lesson’s local runtime or resources to a known starting state without touching unrelated projects.

Command Breakdown

docker: Runs the docker tool with the shown arguments to complete this lesson step.

Expected Result

This lesson’s runtime state is reset or the named lesson container is removed.

What Changed

BeforeThe action shown by this card has not yet been completed or verified.

AfterThe command has completed and the next lesson step has the state it needs.

Verify It

macOSInspect the command output shown above.

LinuxInspect the command output shown above.

Windows PowerShellInspect the command output shown above.

Continue only when the observed result matches the Expected Result block.

If It Fails

Check Docker is running and make sure you are using this lesson’s exact container or launcher name.

What this command does Returns this lesson’s local runtime or resources to a known starting state without touching unrelated projects.

Expected result

This lesson’s runtime state is reset or the named lesson container is removed.

If it fails

Check Docker is running and make sure you are using this lesson’s exact container or launcher name.

Final Check

Prove What You Learned

This lesson contains 4 focused questions. You answered 2 before the build; complete the remaining 2 now.

3 / 4Interview

Why start with simple retrieval?

A beginner can see exactly why a chunk matched.

4 / 4Exam

The handbook is missing and retrieval worsens. What failed?

The relevant information was removed from the retrievable corpus.

Skills you practised

Give AI Your Own Documents

What you'll build

Before You Build

Does the model automatically know local private files?

Why retain the source filename with each chunk?

Mission

Understand

Build

▸Step 1Create the document corpus and retrieval script

Before You Run

Why You're Running This

Command Breakdown

Expected Result

What Changed

Verify It

If It Fails

Before You Run

Why You're Running This

Command Breakdown

Expected Result

What Changed

Verify It

If It Fails

Before You Run

Why You're Running This

Command Breakdown

Expected Result

What Changed

Verify It

If It Fails

Before You Run

Why You're Running This

Command Breakdown

Expected Result

What Changed

Verify It

If It Fails

Before You Run

Why You're Running This

Command Breakdown

Expected Result

What Changed

Verify It

If It Fails

Before You Run

Why You're Running This

Command Breakdown

Expected Result

What Changed

Verify It

If It Fails

Before You Run

Why You're Running This

Command Breakdown

Expected Result

What Changed

Verify It

If It Fails

Before You Run

Why You're Running This

Command Breakdown

Expected Result

What Changed

Verify It

If It Fails

Before You Run

Why You're Running This

Command Breakdown

Expected Result

What Changed

Verify It

If It Fails

Break

Before You Run

Why You're Running This

Command Breakdown

Expected Result

What Changed

Verify It

If It Fails