Learning in the Lab¶
This page walks you through a full learning session – from catalog to completed task.
1. Pick a module from the catalog¶
After login you land in the catalog at techlogia.de/lab/lessons. All available modules appear as cards.
Each module card shows:
- Title of the module
- Difficulty (Beginner, Advanced, Expert)
- Estimated duration (typically 30–60 minutes)
- Your progress (how many tasks passed)
Click a card to open the lesson.
Class students may see fewer modules
If your teacher hid certain modules for your class, they don't appear in the catalog. That's normal and can vary by class.
2. Start a practice VM¶
In the catalog click Start now (or Continue) on a module. The Lab now does several things:
- Check practice time – the catalog shows at the top how much practice time you have left today, e.g. “112 of 180 min of practice time left today. Only time while your practice VM is running counts – a start lasts up to 60 min.” If it is used up, you'll see a notice.
- Check terms status – on a new terms version, a modal appears with the current text.
- Check parental consent – for self-registered learners under 16 the consent of their legal guardians must be in place. For class-code accounts the Lab does not ask for parental confirmation.
- Provision a VM – a Linux VM in Germany boots. Takes 60–90 seconds.
During provisioning you see a progress hint. You can safely switch tabs – the VM keeps running in the background.
Cost note
Each session triggers variable cloud cost (typically under €0.50 per session). This is free for you as a learner – Techlogia covers it. The practice time limits the platform's effort.
3. Understanding the learning environment¶
Once the VM is ready you see the environment in two columns:
- Left: the lesson – the explanation with commands you can run with one click (Run in terminal) and below it the lesson's tasks, each with Validate and hints
- Right: two tabs – Terminal (a real Linux terminal) and Editor (VS Code) for editing files
- Far left, the bar: Modules, Review, My progress, Invite friends, Support, Settings, Leaderboard, My data and Help & Docs
At the very top you'll see a countdown with the remaining time of your practice VM and the End practice VM button.
4. Working in the terminal¶
The terminal is a real Linux on a cloud VM, not a simulator. You have:
sudo– you are a privileged user- Internet – installing packages works (
apt,curl, …) - Temporary files – everything you put under your home is gone after session end
Typical commands that work in the Lab:
sudo apt-get update
sudo apt-get install -y nginx
sudo systemctl status nginx
nano /etc/nginx/sites-available/default
cat /home/student/uebung/hallo.txt), output from the Linux system, new prompt.Terminal tips¶
- Copy/paste:
Ctrl+Shift+CandCtrl+Shift+V(Linux/Windows) orCmd+C/Cmd+V(Mac) - Multi-line: Multi-line text can be pasted as a block.
- If the terminal hangs: Click into the terminal, press Ctrl+L or reload the page – the session stays active.
Editing files (“Editor (VS Code)” tab)¶
Next to the lesson you'll find two tabs: Terminal and Editor (VS Code). The editor is a full VS Code running directly on your practice VM. The Explorer on the left shows the folders and files in your home directory.
- The first time you open it, your VM downloads and starts VS Code. This takes about 20 seconds; you can keep using the terminal in the meantime.
- Open and save as usual: click a file, save with Ctrl+S (Mac: Cmd+S).
- A terminal inside the editor: Terminal → New Terminal gives you an extra console at the bottom of the editor – it runs on the same VM.
- More space: Open in new window (top right) shows the editor in its own browser tab.
- System files (e.g. under
/etc) can be viewed but not saved in the editor – it runs as your userstudent. Usesudoin the terminal as before. Handling permissions is part of what you learn here. - What is kept: Whatever is in
~/ablageis kept for your next start (max. 5 MB). Everything else disappears with the practice VM. - If the editor does not start, it tells you why. Open simple file editor still lets you edit your files: a plain file tree with an editor, files up to 1 MB.
hallo.txt is open, a terminal runs inside the editor below. “Reload” and “Open in new window” sit at the top.5. Checking tasks¶
When you think you've solved a task, click Check below it. The Lab runs an automatic test inside your VM and shows the result:
A green box appears with "Task passed". The task is marked ✓ in the list. You can continue with the next task.
A red box appears with concrete feedback – for example:
"nginx is installed but does not listen on port 80. Check the configuration in
/etc/nginx/sites-available/default."
Fix the problem in the terminal and click Check again.
Order
You can check tasks in any order. There is no hard precondition. Some tasks build on each other conceptually – the lesson description gives a recommendation.
6. Using hints¶
If you're stuck, expand the hints. Each task has up to three levels:
| Level | Content |
|---|---|
| Hint 1 | Light nudge – usually a question or a concept |
| Hint 2 | Concrete example – usually a command or config snippet |
| Hint 3 | Step-by-step solution |
Hints expand on click. There is no penalty for using hints – they are a learning aid.
7. Ending a practice VM¶
There are three ways to end a session:
- End yourself – click End practice VM in the countdown header and confirm with End. The VM is deleted immediately.
- Auto-end after 60 minutes – a warning appears two minutes before. If you do nothing, the session ends automatically.
- Close the tab – if you close the browser tab, the session runs until the 60-minute limit. On re-login you can resume (resume card).
Progress vs. VM content
Your progress (which tasks are passed) is kept permanently. The VM contents (files, installed packages) are gone as soon as the session ends.
8. Resume an active session¶
If you log in again while a session is still active, you'll see a card Resume active session at the top. One click brings you back into the running lesson – without starting a new session and without quota consumption.
9. Giving feedback¶
The player has a feedback button. Use it to:
- Report content errors (e.g. wrong instruction)
- Suggest improvements
- Describe validator issues
Up to 5 feedback entries per day. The Techlogia team reads all input.
FAQ while learning¶
"Validator says passed but my solution looks wrong"¶
The validator only checks the defined outcome. An unusual solution can be perfectly correct. Re-read the task description – sometimes it hints at how an outcome should be achieved.
"Validator says not passed but I'm sure it's right"¶
Look closely at the feedback – often one detail is missing (e.g. a service restart command). If you're sure the validator is wrong, use the feedback button – the team checks it.
"VM provisioning takes forever"¶
60–90 seconds is normal. If nothing happens after 3 minutes:
- Provisioning fails → the lesson shows the reason. If it was our fault (outage, maintenance), the attempt does not count towards your quota and you can start again right away. If you have reached your own daily VM limit, you can continue the next day.
- If errors persist: send feedback or contact info@techlogia.de directly
"I accidentally clicked End"¶
You need to start a new session. If you have no quota left today, your task list is still valid – you can continue exactly there tomorrow.
"How long does a session actually run?"¶
60 minutes from the moment the VM is ready (not from provisioning start). The countdown shows the remaining time at the top of the environment.
Next step¶
- Progress & homework – statistics, achievements and assignments from your teacher.
- Account & privacy – password, two-factor login, account management.