Teachers

Week 14 Overview

This is the final week of the curriculum. You already have a live portfolio (built with Vite, React, and TypeScript) deployed on Vercel — you pushed code, it built, and it appeared on the internet. This week is about everything that happens between those two moments: the automated checks that run before your code is allowed to ship, the configuration that lets the same codebase behave differently in different places, and the security habits that keep what should be private actually private.

None of this is about writing more features. It's about the invisible infrastructure that makes shipping code safe, repeatable, and boring — in the good way. By the end of the week you'll be able to read a CI pipeline instead of being intimidated by it, reason about environment variables instead of guessing at them, and spot the kind of security mistake that quietly ships to production more often than you'd think.

Learning Goals

Understand what CI/CD means and why teams rely on it; as a practice, not just a pipeline
Understand trunk-based development and why long-lived branches work against Continuous Integration
Recognise feature flags as the mechanism that lets teams merge unfinished work to trunk safely
Read and fix a GitHub Actions workflow file
Explain why npm ci runs in automated environments instead of npm install
Understand environment variables and the difference between development, test, and production
Distinguish between public (VITE_*) client-side variables and private, server-only variables
Recognise and prevent the risk of leaking secrets in an API response
Understand what happens when a deployment fails on a platform like Vercel

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.