Week 5 - Containers & CI/CD

Intro: Containers and CI/CD

Dependency Management

Docker Fundamentals

Azure Container Registry

Python CI Pipeline

Practice

Assignment: Containerize and Ship

Gotchas & Pitfalls

Slides (PDF)

Career relevance: Week 5

Glossary: Week 5

Going Further

History of Containers and CI/CD

Slides (PDF)

The slide deck used in the Week 5 in-class kickoff session. The deck covers: welcome back + recap, the live quiz, chapter-by-chapter tour (Ch1-Ch5), two live exercises from the practice chapter, the agenda card, the assignment scaffold tour, and the closing hand-written reflection.

<aside> ๐Ÿ’ก Use this as a recap. If you missed class or want to re-walk the agenda, the deck mirrors the structure of the lesson: same section numbers, same order. Especially useful for the assignment-launch walk-through (ยง9) when you start the assignment at home.

</aside>

Download

week_5__presentation.pdf

week_5__presentation.pdf

What's in it

The slides are deliberately student-facing only. The teacher's per-section script (pacing, quiz answer cribs, exercise reference solutions, deep-dive default topics, closer rubric) lives in the GitHub-only week_5__lesson_plan.md (visible on GitHub only; not synced to Notion, so no link from this page).

Practice exercises (referenced in the live exercise slides)

The two live exercises the deck showcases come from the Learning-Resources repo:

Section Exercise What you practice
ยง3 Live Exercise A (recommended) Ex 1: Minimal Pipeline to Container Write a Dockerfile from scratch and run the container with env vars
ยง7 Live Exercise B (recommended) Ex 5: CI Smoke Test Add a GitHub Actions workflow and confirm it goes red on a broken test

The teacher chooses which to run live based on quiz wrong-pick patterns. Solutions live in each exercise_N/solutions/ folder.


The HackYourFuture curriculum is licensed underย CC BY-NC-SA 4.0 *https://hackyourfuture.net/*

CC BY-NC-SA 4.0 Icons

Built with โค๏ธ by the HackYourFuture community ยท Thank you, contributors

Found a mistake or have a suggestion? Let us know in the feedback form.