How aggressivehiker/rhcsa9 works
Project Type and Purpose
• This repo is a documentation-centric “study guide” for RHCSA 9 exam preparation.
• It is organized as a static collection of Markdown files (no code to compile, no web framework).
• Purpose:
• Provide study notes (“Study Notes” folder),
• How to set up your lab environment (“Lab Setup” folder),
• Offer a practice task list and solutions (“Exam Prep” folder).
File Structure
• Top-level folders:
• study_notes/ – miscellaneous markdown study guides
• lab_setup/ – instructions & artifacts for building a two-node lab (repo container + server1 + server2)
• exam_prep/ – ordered and objective-based task lists, solutions
• lab_setup/repo contains Containerfile (builds a local YUM/DNF-style repository) plus docs on DVD and NFS-based repository creation.
• lab_setup/server1 and server2 each have a README (likely role-specific configuration).
• No dynamic code; everything is static Markdown.
README for Additional Insights
• The top-level README clarifies the three main areas.
• It does not reference a specific static-site generator; assume end users browse on GitHub or clone locally.
Elements
• Clear labels for each folder/component (e.g., “exam_prep/”, “lab_setup/repo/Containerfile”, “Server1”)
• GitHub → User (clone/browse)
• Container build → Package repo service
• Package repo → Server1 & Server2 (mount, yum install)
• Blue for static content components
• Green for lab compute nodes
• Orange for container-based repo service
Detailed Breakdown
• Study Notes (blue)
• Exam Prep (blue)
• Lab Setup (blue)
• Under Lab Setup, break into three green/orange blocks in a row:
• Repo Container (orange, built via Containerfile)
• Server1 (green)
• Server2 (green)
• From Repo Container to both Server1 & Server2 labeled “yum/dnf repo”
• From GitHub Repo to User labeled “git clone / browse docs”