|
| 1 | +# Day 12 – Breather & Revision (Days 01–11) |
| 2 | + |
| 3 | +## Goal |
| 4 | +Take a **one-day pause** to consolidate everything from Days 01–11 so you don’t forget the fundamentals you just built. |
| 5 | + |
| 6 | +## Expected Output |
| 7 | +- A markdown file: `day-12-revision.md` |
| 8 | + (bullet notes + checkpoints) |
| 9 | +- Optional: screenshots of any re-runs you do |
| 10 | + |
| 11 | +## What to Review (pick at least one per section) |
| 12 | +- **Mindset & plan:** revisit your Day 01 learning plan—are your goals still right? any tweaks? |
| 13 | +- **Processes & services:** rerun 2 commands from Day 04/05 (e.g., `ps`, `systemctl status`, `journalctl -u <service>`); jot what you observed today. |
| 14 | +- **File skills:** practice 3 quick ops from Days 06–11 (e.g., `echo >>`, `chmod`, `chown`, `ls -l`, `cp`, `mkdir`). |
| 15 | +- **Cheat sheet refresh:** skim your Day 03 commands—highlight 5 you’d reach for first in an incident. |
| 16 | +- **User/group sanity:** recreate one small scenario from Day 09 or Day 11 (create a user or change ownership) and verify with `id`/`ls -l`. |
| 17 | + |
| 18 | +## Mini Self-Check (write short answers in `day-12-revision.md`) |
| 19 | +1) Which 3 commands save you the most time right now, and why? |
| 20 | +2) How do you check if a service is healthy? List the exact 2–3 commands you’d run first. |
| 21 | +3) How do you safely change ownership and permissions without breaking access? Give one example command. |
| 22 | +4) What will you focus on improving in the next 3 days? |
| 23 | + |
| 24 | +## Suggested Flow (30–45 minutes) |
| 25 | +- 10 min: skim notes from each day, update Day 01 plan if needed. |
| 26 | +- 15–20 min: rerun a tiny hands-on set (process check, service check, file permission change). |
| 27 | +- 5–10 min: write the self-check answers and key takeaways. |
| 28 | + |
| 29 | +## Tips |
| 30 | +- Keep it light—this is about retention, not new concepts. |
| 31 | +- If something felt shaky this week (e.g., `chmod` numbers, `journalctl` flags), practice that specifically. |
| 32 | +- Small wins: one screenshot of a command rerun + 5 bullet notes is enough. |
| 33 | + |
| 34 | +## Submission |
| 35 | +1. Navigate to `2026/day-12/` |
| 36 | +2. Add `day-12-revision.md` with your bullets and answers |
| 37 | +3. Commit and push to your fork |
| 38 | + |
| 39 | +## Learn in Public |
| 40 | +Post 2–3 lines on what you reinforced today and one command you now remember confidently. |
| 41 | + |
| 42 | +Use hashtags: |
| 43 | +#90DaysOfDevOps |
| 44 | +#DevOpsKaJosh |
| 45 | +#TrainWithShubham |
| 46 | + |
| 47 | +Happy Learning |
| 48 | +**TrainWithShubham** |
0 commit comments