Catching a Broken Release Before It Goes Live is a practical DevOps project for learners with basic terminal familiarity. Protect FIELDNOTES, a demonstration museum website, so a polished homepage cannot hide broken visitor directions or downloads.
Two Guided Labs teach business assertions and a local release gate. One independent Challenge extends the same methods to a step-free access guide. You will publish the exact package that passed checks, even when an editable draft changes afterward.
What You Will Learn
- Check real visitor pages, links and downloaded content through HTTP.
- Distinguish a missing resource from a successful response containing wrong information.
- Write small Python assertions and validate them against good and bad packages.
- Use Bash exit status, conditional execution and a shared candidate argument to control publication.
- Preserve complete working visitor paths while delivering the tested package.
Who This Course Is For
This course is for DevOps beginners who can enter commands in a terminal. No prior Python, Bash scripting, Docker or hosted CI experience is required; the small amount of code and syntax is explained before use.
LabEx provides independent prepared Linux environments with Workstation, Live Website and Candidate Preview tabs. No local installation or external account is needed. The website, interface labels and command output are in English; lesson documents and complete challenge solutions are available in eight additional languages.
Frequently Asked Questions
Do I build the museum website?
No. Its complete pages, local illustration, styles and candidate packages are provided. You edit a small test and a short release script.
Is this GitHub Actions or a production security system?
No. This local runner makes business checks, failure decisions and saved-package delivery observable. It does not teach hosted CI configuration, artifact signing, access control or database migration rollback.
How does the Challenge extend the Guided Labs?
It changes the protected journey to step-free access. You combine the same HTTP assertions and package argument flow to reject misleading content while preserving the general visitor service.
