Lab help — one step at a time

Choose your session below. These guides explain the same assignments in smaller steps; using them does not add work or change the review criteria. Mac, Linux and Windows routes are included where commands differ.

Find your walkthrough

Save your work

For practice Sessions 01–11, use your editor or file manager to create submissions/session-NN inside your local course copy, replacing NN with the two-digit session number. Create a note and copy only that session's needed templates. The course's submissions/ directory is Git-ignored scratch space; saving there does not submit or publish anything. Keep your own backup outside the public repository.

Edit Markdown (.md) as ordinary text in your editor. The website and its Markdown reader display documents; they do not edit or save your local work. On Windows, show file extensions so notes.md does not accidentally become notes.md.txt. A browser-based document is fine for drafting; export/copy your work into the required packet format before review.

Session 00's readiness card stays private. Session 12's product and evidence stay in your own product repo. For practice packets, follow the submission guide, including the preflight before a first public upload. Your instructor supplies your cohort code and alias privately. Do not make up a cohort or submit to the curriculum repository.

Know where you are working

Place	Purpose
https://learn.labalicious.com/	Public lessons, instructions and reference material
Your extracted/cloned course folder	Practice source files and local scratch work
http://127.0.0.1:4178	The practice app, after you start its local server
Your AI client	Prompts, explanations and approved tool assistance
The lab-submissions repository	Reviewed practice packets, after privacy preflight
Your own product repository	Course-long software, branches, PRs and milestones

Do not confuse the course website with the local app. Seeing the course website does not mean the local server is running. Practice candidates intentionally include defects; observing an app failure may be part of the assignment rather than a setup problem.

Ask for useful help

After one careful retry, pause and send your instructor or coach:

Session and step:
OS and shell/browser:
What I tried (exact command or click):
What I expected:
What actually happened (sanitized error):
What I have already checked:

Use fictional data only. Crop screenshots to the relevant app and remove usernames, private tabs, tokens and account details. Do not send passwords or recovery codes. A blocked step can be recorded as pending; do not invent evidence to finish the checklist.

For AI coaching, provide only the assigned handout, approved evidence and your draft. Ask for one hint or clarification at a time, then perform the check yourself. Do not provide instructor answer keys or reviewer labels to a model being evaluated. Keep normal permission checks; do not grant access to your whole home folder or unrelated work.

Platform troubleshooting · Working with a coach · Course overview