How tuannmdev/devops-exercises works
Project type and purpose
• This is an open-source “learn-by-doing” repository housing DevOps/SRE interview questions, exercises, tutorials, and certification prep.
• It uses Markdown for content, Bash/Python scripts for automation, and CI pipelines for testing and quality gates.
File-structure analysis
• Top-level directories:
– topics, exercises, certificates: static content (Markdown, code samples, Terraform, Pulumi).
– scripts: automation scripts (shell, Python).
– tests: unit tests and syntax linters.
– images: static assets for documentation and apps.
• Config files & workflows: .github/workflows/ci_workflow.yml, .travis.yml, run_ci.sh – define CI jobs.
• Contribution metadata: CONTRIBUTING.md, LICENSE, .gitignore.
Key README insights
• Describes content categories (DevOps, AWS, Kubernetes, etc.) and mobile apps that consume this repo.
• Indicates CI/CD integration (Travis, GitHub Actions) and guidelines for adding new content.
• Purpose: document management pipeline + distribution via GitHub, GitHub Pages, mobile apps.
a. Main components
– Contributors (People)
– Source Control (GitHub Repository)
– CI/CD System (GitHub Actions, Travis CI)
– Automation Layer (scripts shell/Python)
– Test Layer (unit tests, syntax checks)
– Content Store (Markdown files + images)
– Distribution Channels (GitHub Pages or static hosting, mobile apps on Play Store)
– End Users (learners browsing docs or using apps)
b. Relationships and data flow
1. Contributors push commits to GitHub
2. GitHub triggers CI pipelines (.github/workflows, Travis)
3. CI invokes automation scripts (run_ci.sh, question_utils.py), runs tests (tests/)
4. If all checks pass, content merges into main branch
5. Publishing step (static site generator or direct Markdown render) updates hosted docs
6. Mobile apps periodically fetch or bundle content from repo
7. End users access content via website or mobile apps
c. Architectural patterns
– GitOps: repository as single source of truth
– Doc-as-code: content alongside code, versioned and tested
– CI/CD pipeline enforcing quality and automating publication
d. Key technologies
– GitHub + GitHub Actions, Travis CI
– Bash + Python scripting
– Markdown, static site generation (implied)
– Mobile apps (Android) as downstream consumers