How happyhackinghigh/myfirstsecurity works
Project type and purpose
• This repo is not a conventional code-base but a structured collection of cybersecurity training materials, slide decks, labs and VM images.
• Its purpose is to host and organize course modules (e.g. “From Linux To CTF”, “MyFirstAI”, “MyFirstWebSecurity”), provide links to virtual machine images, CTF platforms, surveys and reference docs for students.
File structure
• Top-level directories correspond to course modules (“Cource”, “From Linux To CTF”, “MyFirstAI”, etc.).
• Each module folder contains markdown lessons, PDFs, PPTX slide decks, code samples or VM download links.
• A handful of “global” files (README.md, various .pptx installers) describe environment setup.
• No compiled code, no server-side scripts—this is purely content.
README for additional insights
• The README lists:
• Links to the live CTF/training platform (URLs and IPs)
• Downloadable VM images (Ubuntu, Kali) with credentials
• Links to surveys and announcements
• It implies external services (web CTF portal, OVA download server) as part of the learning workflow.
a. Main components:
• Learner’s workstation (with VirtualBox/VMs)
• Content repository (this GitHub repo)
• Download server (HTTP host for OVA images)
• CTF platform (web service at 140.110.112.27)
• Survey endpoints (tinyurl links)
• Optional external news sources (ithome.com.tw)
b. Relationships & interactions:
• Learner clones/pulls the repo → reads lessons & slide decks
• Learner downloads OVA from the download server → imports into VM host
• Learner connects VM → accesses CTF platform over the internet
• Learner submits survey responses → survey service
• Instructor updates repo → GitHub hosting → triggers student pull
c. Architectural patterns/design principles:
• Content Distribution: Git (version control) + HTTP file server + static file hosting
• Client-server interactions: learner VM ↔ CTF web service
• Separation of concerns:
– Static content vs. dynamic service (CTF portal) vs. VM imaging
d. Key technologies/frameworks:
• Git/GitHub for content versioning
• HTTP(S) for OVA distribution
• VirtualBox or VMware for training VMs
• Static Markdown and PPTX for lesson delivery
• Web survey services (TinyURL links)
Essential architectural elements
• External dependencies: VM host, CTF portal, survey endpoints.
• Student’s workflow from cloning materials to completing exercises.
• Do not over-complicate: break the system into content storage, distribution, runtime environment, and assessment/feedback components.